JIRA status
Overview
Below tables outline JIRA statuses used by development teams.
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. There are no user stories defining the feature. |
In Refinement | Feature is better defined and ready for the development team to review, to create user stories, and to estimate stories. The PO should have some (UI) user stories defined for this feature and is actively working on further user story refinement. Overall, user story creation and refinement is happening with this status. |
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/UAT review implementation. Reported bugs or enhancements may be in progress at this status. |
Closed | PO approves implementation for release. |
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 | In Dev Review |
Prep Deployment | Some teams use this when the code has been merged but not yet available on a hosted reference environment for a PO to review. |
In QA | In QA Review |
In Review | PO/SME review implementation. |
For Release | Can use if issue PO needs to write documentation and/or test case (used by ERM dev team 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. |