Jira is a powerful project management tool used by teams worldwide to track issues, and projects.
One of the core features of Jira is its ability to help teams define and track the status of each issue as it moves through different stages of a workflow. Understanding how these statuses work and how they impact integrations with tools like Gearset can help ensure smoother project management and deployment processes.
What are Jira statuses?
A Jira status represents the current stage of an issue in its workflow. Workflows in Jira are highly customizable, allowing organizations to define statuses that reflect their specific processes. An issue status is changed as it progresses from creation to completion, helping teams track the lifecycle of an issue.
Common Jira statuses and their meanings:
While Jira workflows are flexible, certain statuses are common across many teams. Here’s a breakdown of some widely used statuses:
To Do: The issue has been created but no work has started yet.
In Progress: Work on the issue has begun.
Done: The issue has been resolved or completed, and no further action is required.
This sample Jira workflow demonstrates how each status has been configured.
It's also key to note the accepted 'Transition' routes from one status to another, as these can prevent the successful move for a ticket into a new status.
Issues retrieved in Pipeline for creating branches
In the Gearset Pipeline, Jira issues are retrieved and selected to create branches with matching names.
Only issues that do not have the 'Done' status in Jira are included, ensuring that work is focused solely on active issues requiring further attention.
If you require to flag that a pull request has finished it's work but is still pending to deploy it to a live environment, you could create another status but not configure it as Done in Jira.
In the below example a status called "Done pending deployment" was created.
These status are also reflected in the Pipeline settings to configure against each environment.
Find out more about Updating a Jira ticket's status in pipelines
It's important to note that each status is correctly configured in the pipeline to align with the Jira workflow, especially around transitions, in order to ensure that progress tracking functions as expected.