Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Issue Types : Bug, Improvement, New Feature

FromAssignee Transition ToAssignee 
OpenFinance Systems Manager
Approve
→Requires Prioritizationno-change
Reject→IncompleteRequester
Requires PrioritizationFinance Systems Manager
Prioritize
→Available for EstimationTechnical Lead
IncompleteRequestor
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
Development in ProgressDeveloper
Development Complete
→Development Completeno-change
Blocked
→BlockedTechnical Lead
Development CompleteDeveloper
Deploy
→Ready for QARequester
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
→Ready for PRDTechnical Lead
Fail→BlockedDeveloper
Ready for PRDTechnical Lead
Deployment Complete
→PROD Deployment Completeno-change 
Deployment Failed
→Blockedno-change 
PROD Deployment CompleteTechnical Lead
Close
→Closedno-change
ClosedTechnical LeadThere 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
ClosedThere 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
  • 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.
 

 

  • No labels