JIRA status
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 Refinement | Feature 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 Progress | Feature is in development. |
Blocked | Feature is blocked due to a dependency. |
In Review | Development complete. PO/SME review implementation. |
Closed | PO/SME approves implementation. |
JIRA status for all projects except UXPROD
Story JIRA status | When do you set a story to this status? |
|---|---|
Draft | Issue has not been defined. Still very vague. Very little analysis/research has been done. Not ready for development team to review. |
In Refinement | Issue 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). |
Open | Issue is ready for development to begin implementation. |
In Progress | Issue is in development. Assume in current sprint. |
Blocked | Issue 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 Review | Development complete. PO/SME review implementation. |
For Release | Can use if issue PO needs to write documentation and/or test case (used by ERM only at this time) |
Awaiting release | Bugfest/Hotfix workflow step: Issue requires a module release. |
Awaiting deployment | Bugfest/Hotfix workflow step: Issue requires deployment to release's bugfest environment. |
In Bugfix review | Bugfest/Hotfix workflow step: Ready for PO/SME to verify issue has been resolved. PO/SME uses release's bugfest environment for verification. |
Closed | PO/SME approves implementation. |