Issue Types : Bug, Improvement, New Feature
This table describes the standarad operating procedure for JIRA usage. Following procedure is imperative, because the automated merge tool anticipates that this procedure has been followed:
Status | Resolutions | UAT Status | Customization Status | Assignor (who sets the status and assignee) | Asignee (after status set) | |||||
Open | Unresolved | None | Requester | <decided based off of KFS component>** | ||||||
Open | Unresolved | None | Assigned | Technical Manager | Developer/Technician | |||||
In Progress | Unresolved | None | Development in Progress | Developer | Developer | |||||
In Progress | Unresolved | None | Development Complete | Developer | Developer | |||||
In Progress | Unresolved | None | Unit Testing Complete | Developer | Developer | |||||
In Progress | Unresolved | None | Deployed to UAT | Developer | Requestor | |||||
In Progress | Resolved | Passed | User Accepted | Requestor/tester | Developer/Technician | |||||
In Progress | Unresolved | Failed | User Rejected | Requestor/tester | Developer/Technician | |||||
Closed | Resolved | Passed | Deployed to PRD | Developer/Technician | ||||||
Open || In Progress || Re-opened | Unresolved | Any | On Hold | Developer/Technical Manager | Developer | |||||
From | Transition | To | Assignor (who sets the status and assignee) | AssigneeFrom | Assignee | Transition | To | Assignee | ||
---|---|---|---|---|---|---|---|---|---|---|
Open | Finance Systems Manager | Approve | → | Requires Prioritization | no-change | |||||
Reject | → | Incomplete | Requester | |||||||
Requires Prioritization | Finance Systems Manager | Prioritize | → | Available for Estimation | Technical Lead | |||||
Incomplete | Requestor | 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 | ||||||
Development in Progress | Developer | Development Complete | → | Development Complete | no-change | |||||
Blocked | → | Blocked | Technical Lead | |||||||
Development Complete | Developer | Deploy | → | Ready for QA | Requester | |||||
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 | → | Ready for PRD | Technical Lead | |||||
Fail | → | Blocked | Developer | |||||||
Ready for PRD | Technical Lead | Deployment Complete | → | PROD Deployment Complete | no-change | |||||
Deployment Failed | → | Blocked | no-change | |||||||
PROD Deployment Complete | Technical Lead | Close | → | Closed | no-change | |||||
Closed | Technical Lead | There are no transitions out of this status |
Issue Types : Data, Process, Task, Subtask, Other
Open | Reject | → | Incomplete | @Bret | |
Approve | → | Requires Prioritization | |||
Requires Prioritization | Prioritize | → | Available for Estimation | ||
Incomplete | Re-Open | → | Open | ||
Available for Estimation | Estimate | → | Available for Assignment | ||
Available for Assignment | Assign | → | To Do | ||
To Do | Start Development | → | Development in Progress | ||
Development in Progress | Development Complete | → | Development Complete | ||
Blocked | → | Blocked | |||
Development Complete | Deploy | → | Ready for QA | ||
Blocked | Development Issues Resolved | → | To Do | ||
QA Issues Resolved | → | Ready for QA | |||
Need More Requirements | → | Incomplete | |||
Ready for QA | QA Started | → | QA in progress | ||
QA in progress | Pass | → | Ready for UAT | ||
Fail | → | Development in Progress | |||
Ready for UAT | UAT StartedNo Screen | → | UAT in Progress | ||
Ready for PRD | Deployment CompleteNo Screen | → | PROD Deployment Complete | ||
Deployment Failed No Screen | → | Blocked | |||
Closed | There are no transitions out of this status | ||||
PROD Deployment Complete | Close No Screen | → | Closed | ||
Closed | There are no transitions out of this status | ||||
UAT in Progress | → | Ready for PRD | |||
Fail | → | Blocked |
...
Fail
...
Finance Systems Manager - Brett
Technical Lead - Rich
Developer - Kathy, David, Paul, Rich
Requester - Brett, Jean, Bruce, Michael
Subject Matter Expert - Annette Pavone, Lori Hansen, Terri Richard, Rita Parciak, Nancy Patrylak, Jeremiah Macht, Dave Ferreira, Carleen Wells, Nicole Kulig, Angela Piela, Ann Jordan, Alyse Lofman-Kwapien, Kelly Wihbey
Pre-Build
Verify that all Jira’s owned by you (you are the assignee) reflect the proper values for selection by the automated tool:
...
- Perform a unit test to verify that the changes and all dependencies are in place.
- Verify that the customization status is “Deployed to UAT”
- Assign the Jira to the requestor providing comment informing them that the change is in UAT and ready for their validation. Also tell them the date of the next scheduled PRD build so they know what their target completion for testing is.