Page Comparison

Our Bug tracking App lets you keep track of all reported bugs and defects in software development projects.

Image Added

Bug App

Each bug has the following associated information as custom fields:

• Bug Type
• Severity
• Component
• Resolution
• Affects Version
• Fix Version

Workflow Steps:

...

1. User QA member reports a bug.
2. Bug is set in the 'In VerificationReported' state and assigned to the QA Manager (defined as a State Manager) who can do one of the following
   
   1. Seek further clarification on the bug from the client
   2. Assign to someone from his/her team for verification
   3. Verify themselves if it is a bug or not
3. If Not a bug, then Close the item and inform the user
4. Otherwise flag it as a Bug and assign to someone from the Engineering team who will work on the fix
5. When fixed, they can mark it Ready for Retest and assign to someone from QA team who will test the fix
   
   1. If fixed, then QA can mark as the bug as Passed and close it, informing the user.
   2. If not fixed, then QA can mark the bug as Failed and assign back to Engineering for fixing
   3. Engineering can fix the bug and mark it for Retest, assigning it back to the QA

Image Removed

1. a development team member. The developer can
   
   1. Fix the bug and mark it as 'Resolved'
   2. 'Close' it stating it is not a bug.
2. In 'Resolved' state, the QA member can either reopen the bug or close it.