Possible statuses can include in workflow in Jira

In Jira, the possible statuses that can be included in a workflow depend on the customization and configuration of the specific project. However, there are some common default statuses that are available in most Jira instances. These common statuses include:

  1. Open: The initial status of an issue when it is created.
  2. In Progress: The status indicating that work is actively being done on the issue.
  3. Resolved: The status indicating that the issue has been resolved or completed.
  4. Closed: The status indicating that the issue is considered closed, and no further action is required.
  5. Reopened: The status indicating that the issue was previously resolved but has been reopened for further work.
  6. To Do: An alternative status for the initial state, often used in Scrum boards.
  7. Done: An alternative status to represent completion, often used in Kanban boards.
  8. In Review: A status used to indicate that the issue is under review or being checked by relevant stakeholders.
  9. Blocked: A status indicating that the issue cannot progress due to a blocking issue or dependency.
  10. In Testing: A status indicating that the issue is currently being tested or verified.
  11. In Review: A status indicating that the issue is under review by reviewers or stakeholders before moving to the next stage.
  12. In Development: A status indicating that the issue is currently being actively worked on by the development team.
  13. In Test: A status indicating that the issue is ready for testing and verification.
  14. Verified: A status indicating that the issue has been tested and verified successfully.
  15. Rejected: A status indicating that the issue has been rejected or deemed invalid.
  16. Duplicate: A status indicating that the issue is a duplicate of another issue and will be resolved by referring to the original issue.
  17. On Hold: A status indicating that the issue is temporarily on hold, awaiting further information or resolution of other dependencies.
  18. In Progress – Code Review: A specific status for code review in development workflows.
  19. Ready for Deployment: A status indicating that the issue is ready to be deployed to production.
  20. Postponed: A status indicating that the issue has been postponed to a later date or iteration.

Leave a comment

Your email address will not be published. Required fields are marked *