Page Comparison

Celoxis comes with a basic workflow defined for Bug Tracking. You can modify it to suit your needs. 

You need to initiate a process of type "Bug". For details, click here.

...

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. 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 and inform the customer
4. Else if bug, flag it as a Bug and assign to someone from the Engineering team who will work on the fix
5. When fixed, mark ready for Retest and assign to someone from QA team who will test the bug
   
   1. If fixed, marks as Pass and assigns back to Engineering 
   2. If not fixed, marks as Fail and assigns back to Engineering for fixing
   3. Engineering refixes bug and marks again for Retest and assigns back to QA
6. On Pass, Engineering marks the bug as Closed which assigns it back to the Requestor

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.