Features

• Say the bug out loud

  Dictate the bug in the browser, or type it. Each new phrase is added to the text.

  Why: Testers find most bugs on a phone, where speaking is faster than typing.

• Follows the repo's own template

  GitIssue reads the issue templates, CONTRIBUTING and README of the repo, and fills the template it finds.

  Why: Maintainers triage faster when each issue has the format and the fields that they asked for.

• Real screen names from the code

  GitIssue scans the screen and route files of the repo, and keeps only the names that it finds in the code.

  Why: A developer can go to the correct file at once, and the AI cannot invent a screen.

• Duplicate check before you post

  Open and closed issues are searched for the same bug, and the possible matches show before the draft.

  Why: One issue with all the findings is more useful than three issues that say the same thing.

• Comment, reopen or file a regression

  When the bug is already reported, you add your findings as a comment. You reopen a closed issue if you can, or file a new issue that links to it.

  Why: A bug that comes back gets attention in the correct place, with its history.

• Saved devices

  Detect the device and browser you test on in one tap, or enter it by hand. Saved devices can be picked for each report.

  Why: The device and OS version are the details that bug reports most often forget.

• Screenshots

  Paste, pick or take up to 5 images. They go into the issue where the template asks for them.

  Why: A picture shows the bug faster than a paragraph.

• You approve each post

  You see and edit the full draft, or ask for a change in plain words. Nothing goes to GitHub until you tap Post.

  Why: The issue is posted with your name, so you have the last word.

• URL shortcut

  On any GitHub repo page, change github.com to the GitIssue address to open the report form for that repo.

  Why: You can start a report from the page you already have open.

• Drafts stay on your device

  Your text, screenshots and draft are kept in this browser until you post or discard them.

  Why: A refresh, a sign-in or a limit does not lose your work.

• No account before the first step

  You can open a repo and describe the bug first. GitIssue asks you to sign in with GitHub only when you want the draft.

  Why: You can try the app before you give it access to anything.

• My reports

  A list of each issue you created, reopened or commented on through GitIssue.

  Why: You can follow up on your reports from one place.

Have a question? See the FAQ, or read how it works.