JIRA Workflow

Owned by Richard Ritchie
Last updated: Nov 03, 2016
1 min read

This is the standard workflow used for Issue Types : Bug, Improvement and New Feature

FromAssignee Transition ToAssignee  Comments
OPENFinance Systems Manager
Approve
→Requires Prioritizationno-change 
Reject→INCOMPLETERequester 
Requires PrioritizationFinance Systems Manager
Prioritize
→AVAILABLE FOR ESTIMATIONTechnical Lead 
INCOMPLETERequester
Re-Open
→OPENFinance Systems Manager 
AVAILABLE FOR ESTIMATIONTechnical Lead
Estimate
→AVAILABLE FOR ASSIGNMENTno-change 
AVAILABLE FOR ASSIGNMENTTechnical Lead
Assign
→TO DODeveloper 
TO DODeveloper
Start Development
→DEVELOPMENT IN PROGRESSno-change 
BLOCKEDTechnical LeadDevelopment Issues Resolved→TO DODeveloper 
DeveloperQA Issues Resolved→READY FOR QARequester 
DeveloperNeed More Requirements→INCOMPLETERequester  
DeveloperClose→CLOSEDno-changeResolution=Won't fix
DEVELOPMENT IN PROGRESSDeveloper
Development Complete
→DEVELOPMENT COMPLETEno-change

XML/SQL Required for Build?

Blocked
→BLOCKEDTechnical Lead 
DEVELOPMENT COMPLETEDeveloper
Deploy to UAT
→READY FOR QARequesterFix Version=next release
READY FOR QARequester
QA Started
→QA IN PROGRESSno-change 
QA IN PROGRESSRequester
Pass
→READY FOR UATSubject Matter Expert 
Fail
→DEVELOPMENT IN PROGRESSDeveloper 
READY FOR UATSubject Matter Expert
UAT Started
→UAT IN PROGRESSno-change 
UAT IN PROGRESSSubject Matter Expert
Pass
→USER ACCEPTEDTechnical Lead 
Fail→BLOCKEDDeveloper 
USER ACCEPTEDTechnical Lead
Resolve
→READY FOR PRODno-change Resolution=fixed
READY FOR PRODTechnical Lead
Close
→CLOSEDno-change 
CLOSEDTechnical LeadThere are no transitions out of this status    

 

 

Â