Most of the time we use Github, Gitlab, Asana or Trello boards to manage issues.

Issues steps

• Backlog – The issue has been created.
• In Progress – The Fixer has acknowledged the issue, and has begun working on a fix.
• Not An Issue – The Fixer has determined that the issue is expected or by design.
• Not Reproducible – The Fixer cannot recreate the issue as described.
• Missing Information – The Fixer needs more details in order to complete the fix.
• Pushed Back – The Fixer had previously marked the issue as Not An Issue, Not Reproducible, or Missing Information. The Tester has now provided more details, and wants the Fixer to take another look.
• Ready For Next Release – The Fixer has resolved the issue, but does not want the Tester to be notified yet. Instead, the issue will be added to a Release – a collection of issues that should all be tested at once. When a project administrator creates a Release Build, the Testers of all the issues will be asked to confirm their issues’ fixes.
• Ready For Retest – The Fixer has resolved the issue, and wants the Tester to confirm that the fix also works for them.
• Fix Not Confirmed – The Tester has tried the fix, but the issue is still unresolved.
• Fixed – The Tester has tried the fix, and it has correctly resolved the issue.
• Closed – The issue should no longer be worked on.
• On Hold – The issue will be worked on at a later time.
• Duplicate – The issue is a duplicate of another issue.

Issue templates

Title: [PAGE|SCREEN] : Short but precise object of the issue

Description: In order to accelerate issues spotting you should provide as many details as you can. Please follow the template provided in issue-templates.