GitHub integration

Screenshots are uploaded to GitHub and shown in the issue, which needs one extra GitHub permission. Until it’s granted, the tracker shows Screenshots aren’t attached yet with an Allow button, and screenshots wait.

Teammates with write or admin access to the repository, by mentioning the Rebase app in a comment. Rebase replies with a link to create the packet link, and comments again when the packet arrives.

Only connecting and choosing where reports go is required. Defaults for new issues sets labels and other fields on every issue, report rules pick a tracker for packets and reports sent by hand, and Send new reports here can be switched off. The Packets switch turns requests from comments on or off.

No. Sending starts as soon as a report arrives, once the screenshot is processed. Rebase adds the summary to the issue description in place when it’s ready.

Rebase holds its update until a teammate reviews it, and keeps their edits.

No. Status comes back from GitHub, not the other way. Resolving or reopening a report in Rebase doesn’t change the issue.

Rebase retries temporary failures up to 5 times, at least 2 minutes apart. If it still can’t send, the report shows why, and Owners and Admins get an email.

Yes. Each new report goes to every connected tracker with Send new reports here on, so with two on, each report becomes an issue in both.