Jira Ticket Statuses: A Guide to Each Workflow Stage in Jira
Unsure what a Jira ticket status means? Learn how workflow stages, board columns, and rules connect—read now to track progress and prevent delays.
A Jira issue can look stuck even when someone has updated it. One teammate sees “In Review,” another sees “In Progress,” and a manager cannot tell whether the work is finished.
That confusion can hide delays, muddy reports, and leave tickets waiting for the wrong person. It often starts when status names, board columns, and workflow rules are treated as the same thing.
But here's the truth: a status is one step in a larger workflow. Once you know what each stage means and how Jira connects them, you can read ticket progress more clearly and make workflow changes with fewer surprises.
What a Jira ticket status means
A Jira ticket status is the current stage of an issue in its workflow, such as “To Do,” “In Progress,” or “Done.” It tells you where work stands, while workflow rules determine which stages an issue can enter next.
Jira workflows connect statuses through transitions. A transition is an action that moves an issue between stages. For example, a developer might transition a bug from “To Do” to “In Progress” when work begins.
Each status belongs to a broader category: To Do, In Progress, or Done. These categories help Jira and boards interpret an issue’s overall state, even when teams use different status names.

Status, category, and resolution are different
A status gives an issue its specific stage. A status category groups that stage into a broad state. Resolution records how an issue was settled, such as “Fixed” or “Won’t Do.”
For example, a team might move a bug to “Ready to Deploy,” which falls under the Done category. The issue may still need a resolution value that says “Fixed.” The status and resolution answer different questions.
Common Jira ticket statuses and what they mean
Jira does not require every project to use one universal set of status names. These common stages provide a useful starting point, but your team’s workflow may include extra review or approval steps.
- To Do: The work has been accepted or planned, but nobody has started it yet.
- Selected for Development: The team has chosen the issue for upcoming work, often during sprint planning.
- In Progress: Someone is actively working on the issue.
- In Review: Work is ready for a teammate, reviewer, or stakeholder to check.
- Testing: The change is being checked against expected behavior.
- Blocked: Progress cannot continue until a dependency or obstacle is resolved.
- Done: The team considers the work complete according to its workflow.
- Closed: The issue is formally finished, sometimes after final checks or release.
Here's why: “Done” can mean different things across teams. A software team might require code review and testing before completion, while a support team might consider a request done once it has been answered.
Agree on what each stage means before adding more statuses. If one team member uses “In Review” for peer review and another uses it for customer approval, the label will not provide a reliable picture of progress.
How statuses, transitions, and board columns work together
A workflow defines the statuses available to an issue and the transitions that connect them. A board then displays selected workflow stages as columns. The board is a view of the workflow, rather than a complete definition of it.
For example, a team could have separate “Code Review” and “QA Testing” statuses but show both in one “Review” board column. The detailed workflow remains intact while the board stays easy to scan.
Transitions control movement
Transitions describe how an issue can move from one status to another. Some workflows allow a direct move from “To Do” to “Done,” while others require the issue to pass through development and testing.
A transition can also prompt an assignee, require a field, or trigger an action. A team might require a testing result before moving an issue to “Ready to Release.” That rule can reduce missed checks.
Board columns show a simplified view
Board administrators map statuses to columns. If several statuses share one column, a card can appear in the same visual area even as its exact status changes.
You might be wondering: why does a card say “Ready for QA” when it appears under “In Progress”? The board column may group that status with other active work. Check the issue’s status field for its precise stage.
How to read or change an issue’s status
To understand a ticket’s progress, open the issue and check its current status. Then review its activity or transition history if you need to know who moved it and when.
- Open the issue. Find the current status near the issue’s main details. Its location can vary with the Jira layout.
- Check the available actions. Jira displays the transitions currently available to you, such as “Start Progress” or “Submit for Review.”
- Choose the correct transition. Select the action that matches the work’s real progress, rather than choosing a status just to clear a queue.
- Complete any required fields. A workflow may ask for a resolution, comment, or other detail before it allows the transition.
- Confirm the new stage. Check the issue again and make sure the board and issue view reflect the change you expected.
If a needed transition is missing, you may lack permission, or the workflow may not allow that move. Ask a Jira administrator to check the workflow before making a separate status change or adding a workaround.
For instance, if a completed issue cannot move to “Closed,” the workflow may require a resolution first. Understanding the rule can prevent a cycle of repeated status changes and incomplete tickets.
Design a workflow that gives useful progress signals
A good workflow reflects meaningful changes in responsibility or work state. Adding a status for every small action can make boards harder to scan without making progress clearer.
Start with a simple path, such as “To Do,” “In Progress,” “In Review,” and “Done.” Add a stage when it helps the team make a decision, assign responsibility, or spot a delay.
Make each status easy to interpret
Write a short definition for each status. For example, define “In Review” as work that is complete and waiting for a peer check. That shared meaning helps teammates update issues consistently.
Keep transitions practical
Map the common routes a ticket takes, including what happens when review fails or work is blocked. A bug might move from “In Review” back to “In Progress” when a reviewer finds a problem.
Use workflow conditions and required fields only when they solve a real problem. If moving an issue requires several details that nobody uses, people may delay updates or choose inaccurate stages.
Review the workflow with real tickets
Test proposed changes against a few actual scenarios before rolling them out. Follow a routine task, an urgent bug, and a ticket that needs rework. Notice whether the statuses describe each stage clearly.
Built-in reports can help reveal issues such as work sitting in review for too long. If a report shows many tickets waiting at one stage, check whether that indicates a genuine bottleneck or a confusing status definition.
Jira ticket status management with ONES.com

Value Proposition
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. ONES Project is a Jira alternative for teams seeking configurable workflows, reporting, and deployment choices.
ONES Project and ONES Wiki are sold separately. Teams can use ONES Project to organize ticket stages and project work, while ONES Wiki can hold practical guidance about what those stages mean.
Core Capabilities
- Workflow sprawl: Jira-compatible workflows in ONES Project let teams define practical ticket paths; the result is a status flow that reflects how work moves.
- Unclear stage ownership: Custom workflows let teams shape transitions around their responsibilities; the result is a clearer handoff between people or teams.
- Fields that miss important context: Custom fields provide places to capture relevant project details; the result is more useful information alongside each issue.
- Limited sprint visibility: Sprint management supports planning and tracking sprint work; the result is a clearer view of what the team has committed to completing.
- Manual repeat tasks: Automation can handle selected routine actions; the result is less manual upkeep when issues move through a workflow.
- Scattered progress checks: Built-in reporting gives teams views of project progress; the result is a more direct way to spot delays or review work distribution.
- Plugin dependence: Native capabilities can reduce the need for extra plugins; the result is a more consolidated setup for common project workflows.
- Deployment restrictions: Cloud, On-Premise, Private Cloud, and Air-gapped deployments give teams deployment options; the result is flexibility for different operating environments.
ONES Project offers full feature parity between its cloud and self-hosted versions. A team can consider deployment needs without giving up feature access solely because it chooses a self-hosted option.
Teams can start with the free plan for up to 30 seats. ONES.com’s unified platform also includes ONES Assistant, its AI assistant, while the project and knowledge products remain separately sold.
Application Scenarios
A software team managing review stages: A team can define stages for development, code review, testing, and completion in ONES Project. Custom transitions can make responsibilities clearer, while reporting helps the team notice tickets waiting too long.
A distributed organization standardizing ticket meanings: A project lead can manage issue workflows in ONES Project and keep the team’s status definitions in ONES Wiki. New teammates can refer to the same guidance when updating tickets.
A team with restricted deployment needs: An organization can assess Cloud, On-Premise, Private Cloud, or Air-gapped deployment options. Full feature parity across cloud and self-hosted versions helps it evaluate the environment separately from feature access.
Common challenges with Jira statuses
Too many statuses make boards difficult to scan
Problem: The workflow has a separate status for every minor activity, so teammates struggle to see the overall stage.
Solution: Combine statuses that do not represent a meaningful handoff or decision. Keep detailed steps in team guidance when they do not need their own workflow stage.
Tickets remain in progress after work has stopped
Problem: The status says “In Progress,” but the assignee is waiting for a decision, dependency, or review.
Solution: Define when to use a “Blocked” or “Waiting” status, if the team needs one. Make the reason visible in the issue so others can help resolve the delay.
Board columns and issue statuses seem inconsistent
Problem: A ticket’s exact status does not match the label of the board column where it appears.
Solution: Check the board’s status-to-column mapping. If the grouped view causes confusion, adjust the mapping or explain which statuses share each column.
Completed issues have missing resolution details
Problem: An issue sits in a Done-category status, but reports or filters treat its resolution as incomplete.
Solution: Review the workflow’s completion transitions and confirm they set an appropriate resolution. Keep the team’s resolution choices clear and consistent.
FAQs about Jira ticket statuses
What are the default Jira ticket statuses?
Jira workflows often include statuses such as “To Do,” “In Progress,” and “Done,” but a project’s exact options depend on its workflow. Teams can use additional stages, including “In Review” or “Testing.” If your project uses different names, check the workflow description or ask a Jira administrator to explain what each stage means.
Can a Jira issue have more than one status at a time?
No. An issue has one current workflow status at a time. It may have a status history showing earlier stages, and its board column may group multiple statuses together. That can make the board display look less specific than the issue itself, so check the issue’s status field when you need the exact stage.
Why can’t I change a Jira ticket’s status?
The transition you need may not be available in that workflow, or your account may not have permission to use it. A transition might also require a field or approval before it can continue. Check the available actions and any prompts on the issue. If the expected option is missing, ask a Jira administrator to inspect the workflow and permissions.
What is the difference between a status and a board column?
A status is the issue’s exact workflow stage, such as “Ready for QA.” A board column is a visual area that can represent one or several statuses. For example, a board’s “Review” column might include both “Code Review” and “QA Testing.” Check the issue itself when the precise status matters.
Conclusion
A Jira ticket status tells you the issue’s current workflow stage, while transitions control how it moves and board columns provide a visual summary. Knowing the difference helps you interpret progress, find bottlenecks, and avoid treating every board label as an exact status.
Keep status names understandable, agree on what they mean, and test workflow changes with real examples. When tickets seem stuck or reports look misleading, check the transition rules, board mapping, and resolution details.
That small amount of workflow clarity can prevent confusion from spreading across a project. With the right stages and shared definitions, your team can see where work stands and decide what should happen next.