Issue Types : Bug, Improvement, New Feature
| From | 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 |
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 Started | → | UAT in Progress |
| Ready for PRD | Deployment Complete | → | PROD Deployment Complete |
Deployment Failed | → | Blocked | |
| Closed | There are no transitions out of this status | ||
| PROD Deployment Complete | Close No Screen | → | Closed |
| UAT in Progress | Pass | → | Ready for PRD |
Fail | → | Blocked | |
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:
Jiras going to PRD should always have a fix version assigned that corresponds to the next planned release.
- Fix Version must = next release
- Jira should be Resolved
- Customization status must be “User Accepted”
- UAT Status must be “Passed”
Jiras going to UAT
- Jira must be Unresolved
- Jira must be “In Progress”
- Customization status must be “Unit Testing Complete”
- Are there external file dependencies for deplyment/build? If so set the checkbox & paste svn link to files in JIRA comment, along with instructions & dependencies for execution fo the CM.
Post-Build (any environment)
Verify that the changes and all their dependencies have arrived in the target environment
Verify that any required SQL scripts have been executed without error
Verify that status field values
Post deplyment - PRD – please make sure you take the following actions
- Verify that changes have arrived and are complete (may need to work with requestor)
- Set status to “Closed”
- Verify that customization status is set to “Deployed to PRD”
Post deployment - UAT– please make sure you take the following actions
...
Pre-Release
- Notify testers of issues in UAT that are ready to be tested. Richard Ritchie
- Email notification to developers for code freeze. Richard Ritchie
- Code Freeze (End of Business). Richard Ritchie
- Verify trunk has code from any tagged versions since last major release. Richard Ritchie
- Create Footprints RFC (2503). Richard Ritchie
- Mark RFC as Functionally Approved. Former user (Deleted)
- Create JIRA Task for Tag and Deploy (KPS-349). Assign to Ben. Richard Ritchie
- Final UAT Deployment Benjamin Daniels, David Chudnow (Deactivated)
- Notify testers of issues in UAT that are ready to be tested. Richard Ritchie
- Notify users of upcoming release. Brett Paulson
- Change JIRA issues status to "READY FOR PROD". Richard Ritchie
- Tag and build the scheduled Release. Benjamin Daniels
- Deploy to SUP environment in afternoon. Benjamin Daniels
...
Release
- Perform Deployment. Benjamin Daniels
- Change JIRA issues status to "PROD DEPLOYMENT COMPLETE". Benjamin Daniels
- Release the new version in JIRA. Benjamin Daniels
- Perform Checkout Brett Paulson, Jean Ose
- Notify Users with release notes and dates data will be refreshed. Brett Paulson
- Change JIRA issues status to "CLOSED" Richard Ritchie
...
Post-Release
- Database refresh. Richard Ritchie
- Re-Encrypt UAT data. Richard Ritchie
- Monthly Kuali Audit Report. Kathleen Avery (Deactivated)
...