JIRA Workflow
This is the standard workflow used for Issue Types : Bug, Improvement and New Feature
From | Assignee | Transition | To | Assignee | Comments | |
---|---|---|---|---|---|---|
OPEN | Finance Systems Manager | Approve | → | Requires Prioritization | no-change | |
Reject | → | INCOMPLETE | Requester | |||
Requires Prioritization | Finance Systems Manager | Prioritize | → | AVAILABLE FOR ESTIMATION | Technical Lead | |
INCOMPLETE | Requester | Re-Open | → | OPEN | Finance Systems Manager | |
AVAILABLE FOR ESTIMATION | Technical Lead | Estimate | → | AVAILABLE FOR ASSIGNMENT | no-change | |
AVAILABLE FOR ASSIGNMENT | Technical Lead | Assign | → | TO DO | Developer | |
TO DO | Developer | Start Development | → | DEVELOPMENT IN PROGRESS | no-change | |
BLOCKED | Technical Lead | Development Issues Resolved | → | TO DO | Developer | |
Developer | QA Issues Resolved | → | READY FOR QA | Requester | ||
Developer | Need More Requirements | → | INCOMPLETE | Requester | ||
Developer | Close | → | CLOSED | no-change | Resolution=Won't fix | |
DEVELOPMENT IN PROGRESS | Developer | Development Complete | → | DEVELOPMENT COMPLETE | no-change | XML/SQL Required for Build? |
Blocked | → | BLOCKED | Technical Lead | |||
DEVELOPMENT COMPLETE | Developer | Deploy to UAT | → | READY FOR QA | Requester | Fix Version=next release |
READY FOR QA | Requester | QA Started | → | QA IN PROGRESS | no-change | |
QA IN PROGRESS | Requester | Pass | → | READY FOR UAT | Subject Matter Expert | |
Fail | → | DEVELOPMENT IN PROGRESS | Developer | |||
READY FOR UAT | Subject Matter Expert | UAT Started | → | UAT IN PROGRESS | no-change | |
UAT IN PROGRESS | Subject Matter Expert | Pass | → | USER ACCEPTED | Technical Lead | |
Fail | → | BLOCKED | Developer | |||
USER ACCEPTED | Technical Lead | Resolve | → | READY FOR PROD | no-change | Resolution=fixed |
READY FOR PROD | Technical Lead | Close | → | CLOSED | no-change | |
CLOSED | Technical Lead | There are no transitions out of this status |