Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

Assignee
StatusResolutionsUAT StatusCustomization StatusAssignor (who sets the status and assignee)Asignee (after status set)
OpenUnresolvedNone Requester<decided based off of KFS component>**
OpenUnresolvedNoneAssignedTechnical ManagerDeveloper/Technician
In ProgressUnresolvedNoneDevelopment in ProgressDeveloperDeveloper
In ProgressUnresolvedNoneDevelopment CompleteDeveloperDeveloper
In ProgressUnresolvedNoneUnit Testing CompleteDeveloperDeveloper
In ProgressUnresolvedNoneDeployed to UATDeveloperRequestor
In ProgressResolvedPassedUser AcceptedRequestor/testerDeveloper/Technician
In ProgressUnresolvedFailedUser RejectedRequestor/testerDeveloper/Technician
ClosedResolvedPassedDeployed to PRDDeveloper/Technician
Open || In Progress || Re-openedUnresolvedAnyOn HoldDeveloper/Technical ManagerDeveloper
FromTransition To Assignor (who sets the status and assignee)FromAssignee Transition ToAssignee 
OpenFinance Systems Manager
Approve
Requires Prioritizationno-change
RejectIncompleteRequester
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 ResolvedTo DoDeveloper
DeveloperQA Issues ResolvedReady for QARequester
DeveloperNeed More RequirementsIncompleteRequester
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
FailBlockedDeveloper
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 @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
ClosedThere are no transitions out of this status 
PROD Deployment Complete
Close
No Screen
Closed  
ClosedThere are no transitions out of this status    
UAT in ProgressReady 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.