Page tree
Skip to end of metadata
Go to start of metadata

Overview 

POs have discussed an additional JIRA workflow status that indicates that a feature or story requires more discussion with development and has yet to be estimated. The feature/story is not ready for development to start. The new JIRA workflow status will be named In Refinement. Below tables outline proposed JIRA status workflows' changes. 

NOTE: Please review filters/dashboards/sprint boards once changes are made. 

JIRA status for UXPROD project

Feature JIRA status When do you set a feature to this status?
Draft 

Feature has not been defined. Still very vague. Very little analysis/research has been done. Not ready for development team to review. 

In RefinementFeature is better defined and ready for the development team to review, to create user stories, and to estimate stories. Not ready for development to begin implementation. Feature may need to be further refined. The feature is currently being worked on by team (PO and/or dev). 
Open Feature is ready for development to begin implementation. 
Analysis complete We will no longer use this status. We will sunset with the conclusion of the Lotus release. 
In ProgressFeature is in development.
BlockedFeature is blocked due to a dependency.
In ReviewDevelopment complete. PO/SME review implementation. 
ClosedPO/SME approves implementation. 

JIRA status for all projects except UXPROD

Story JIRA status When do you set a story to this status?
DraftIssue has not been defined. Still very vague. Very little analysis/research has been done. Not ready for development team to review. 
In RefinementIssue is better defined and ready for the development team to review and to estimate issue. Not ready for development to begin implementation. Issue may need to be further refined. The issue is currently being worked on by team (PO and/or dev). 
OpenIssue is ready for development to begin implementation.
In ProgressIssue is in development. Assume in current sprint. 
BlockedIssue is blocked due to a dependency. 
In Code Review
Prep Deployment
In QA

Some teams use this when the code has been merged but not yet available on a hosted reference environment for a PO to review. 

Others may use it if a QA person is assigned to the team and that person is still reviewing implementation. 

In ReviewDevelopment complete. PO/SME review implementation. 
For ReleaseCan use if issue PO needs  to write documentation and/or test case (used by ERM only at this time) 
Awaiting releaseBugfest/Hotfix workflow step:  Issue requires a module release.
Awaiting deploymentBugfest/Hotfix workflow step:  Issue requires deployment to release's bugfest environment. 
In Bugfix reviewBugfest/Hotfix workflow step:  Ready for PO/SME to verify issue has been resolved. PO/SME uses release's bugfest environment for verification.
ClosedPO/SME approves implementation.
  • No labels