Jira Bug flow

 

1. Open(Dev): QA creates a bug ticket, assign it to developer.
   
   
2. On Hold(QA): Developer returns to QA as it's not a bug.
   
   
3. Canceled(QA): QA accepts it is not a bug, or PM thinks it's not a bug.
   
   
4. Pending(PM): QA still thinks it is a bug, let PM make final decesion.
   
   
5. In Progress(Dev): Developer accepts it's a bug and starts fixing it.
   
   
6. Resovled(QA): Developer fixes the bug and assigns back to QA for re-test.
   
   
7. In Testing(QA): QA is re-testing the fixed bug.If failed, return to Developer.
   
   
8. Done(QA): QA verified and passed.

Status	Assignee	Description	Jira Automation
Open	Dev	QA open a new bug and assigne to correspoding Dev.	Assign to specific Dev
On hold	QA	Dev return back to QA and said it’s a not a bug.	Assign back to QA
Canceled	-	QA accepts that it’s not a bug, canceled or PM think a pending bug is not valid.
Pending	PM	QA still thinks it’s a bug and assign to PM for judgement.
In Progress	Dev	Dev starts to fixing the bug.	Auto fill in Dev start date
Resolved	QA	Dev fixed the bug and assign back to QA.	Assign to QA / Auto fill in Dev completed date
In testing	QA	QA starts to verify the bug. If failed, return to In Progress.	Auto fill in QA start date
Done	_	QA verified the bug and passed.	Auto fill in QA　completed date