Jira Statuses Explained: A Workflow Guide for Agile Teams
Unsure what each Jira status means? Learn to create clearer workflows and improve sprint reporting. Click to discover how to use Jira statuses effectively.
Jira statuses tell you where each issue sits in its workflow, from “To Do” through “In Progress” to “Done.” When teams use unclear labels or too many statuses, people struggle to spot blockers, understand ownership, and trust sprint reports. A task marked “Resolved” might still need verification, while another marked “Done” could be waiting for release. These small differences create confusion across boards and reports. But here's the truth: a status works only when everyone understands what it means and what action moves work forward. This guide explains how Jira statuses function, how to choose a practical workflow, and how to avoid common setup problems. You’ll also see examples for Agile teams and learn how another project management platform handles configurable workflows.
What Jira Statuses Mean in an Agile Workflow
Jira statuses are labels that show the current stage of an issue in a workflow, such as “To Do,” “In Progress,” or “Done.” Each status represents a point in the work process, and transitions move issues between statuses.
For example, a developer may move a story from “To Do” to “In Progress.” After implementation, the story could move to “Code Review,” then “Testing,” and finally “Done.” Those stages make progress visible to teammates.
Statuses are part of a Jira workflow, alongside transitions, conditions, validators, and other rules. A board displays issues in columns that usually correspond to workflow statuses or groups of statuses.

Status, transition, and resolution: the difference
A status describes the issue’s current stage. A transition is the action that moves it to another stage. Resolution is a separate field that can indicate how an issue was completed or closed.
Imagine a bug moving from “Open” to “In Progress” after someone starts investigating it. That movement is a transition. The issue’s status becomes “In Progress.” When the bug is fixed, the resolution might be “Fixed,” depending on the workflow setup.
Keeping these terms distinct helps when you troubleshoot reports. An issue may display a closed status while its resolution field remains empty, which can affect filters and reporting.
Statuses and board columns
Jira workflows define the available statuses, while board settings determine how those statuses appear in columns. A board column can represent one status or combine several statuses.
For instance, “Selected for Development” and “To Do” might appear in the same column if your team treats both as work that has not started. Combining them can simplify a board, though it may hide a useful distinction.
Here's why: a status describes workflow state, while a board column is a visual aid. Teams can configure them to serve different purposes without changing what each status means.
Common Jira Statuses and What They Tell Your Team
Most teams need only a handful of statuses to describe their work clearly. The exact labels should reflect your process, rather than copying another team’s setup without considering how work moves.
| Status | Typical meaning | Example signal |
| To Do | The work is accepted or planned, but nobody has started it. | A story is ready for a future sprint. |
| In Progress | Someone is actively working on the issue. | A developer has begun implementing a feature. |
| In Review | The work is awaiting peer review or approval. | A pull request needs review. |
| Testing | The change is being checked against requirements. | A tester is verifying a bug fix. |
| Blocked | Progress cannot continue until a dependency or obstacle is addressed. | A team needs access to a test environment. |
| Done | The issue meets the team’s completion criteria. | Acceptance checks have passed. |
Choose labels that describe observable work
A useful status tells teammates what is happening and what should happen next. “Awaiting Review” gives a clearer signal than “Stage 3,” especially to someone outside the immediate team.
Consider a support team that uses “Waiting for Customer.” The label explains why an issue has paused. A broad label such as “Pending” could mean a customer reply, internal approval, or an unresolved technical dependency.
You might be wondering: should every type of work use the same statuses? Usually, a shared foundation helps teams collaborate. Specialized workflows can still make sense when a process has genuinely different stages.
Understand Jira’s status categories
Jira groups statuses into broad categories, commonly shown as “To Do,” “In Progress,” and “Done.” Individual status names can be more specific while still belonging to one of those categories.
For example, “Code Review” and “Testing” may both belong to the “In Progress” category. The labels show the specific stage, while the category helps Jira classify work more broadly in areas such as board display and reporting.
Check the category when creating or editing a status. A status named “Ready for Release” could be categorized as “In Progress” if work remains, or “Done” if your team considers release readiness complete.
How to Design a Clear Status Flow
Start with the way work actually moves through your team. Then add only the statuses that help people make decisions, coordinate handoffs, or understand progress.
- Map the real stages. Write down what happens between accepting a request and completing it. A feature team might use “To Do,” “In Progress,” “Code Review,” “Testing,” and “Done.”
- Define entry and exit conditions. Decide what must be true before an issue enters each status and what action moves it forward. For example, an issue enters “Testing” after code review passes.
- Keep status names specific. Choose labels that people interpret consistently. “Waiting for Product Review” gives more context than “Waiting.”
- Map statuses to board columns. Make the board reflect the team’s view of work. You could place “Code Review” and “Testing” in separate columns if those handoffs need attention.
- Test the workflow with real issues. Move a few representative tasks through the flow. Check whether the right transitions appear and whether the board shows the expected progress.
- Review the setup after use. Ask the team where work gets stuck or where labels cause questions. Remove or revise statuses that no longer help people act.
Example: a small feature workflow
Suppose a team is building a profile photo option. The story begins in “To Do,” moves to “In Progress” when a developer starts, and enters “Code Review” after implementation.
Once the review passes, the issue moves to “Testing.” If testing finds a problem, the team returns it to “In Progress.” After acceptance checks pass, the story reaches “Done.”
That loop matters. A workflow should show how teams handle rework, not only the ideal path. If a defect sends work back for changes, the transition should be clear and practical.
Set a meaningful definition of “Done”
Agree on the conditions for completion before relying on a “Done” status. For one team, that could mean code is merged and tests pass. Another team may require product approval or a production release.
If every team interprets “Done” differently, cross-team reports become harder to compare. A short shared definition can prevent the same status from representing very different outcomes.
Workflow Choices That Affect Jira Statuses
Statuses are only one part of workflow design. Transitions control how issues move, while workflow rules can determine who can move them and what information they must provide.
Transitions and permissions
A transition can move an issue from “To Do” to “In Progress,” or return it from “Testing” to “In Progress.” Teams can also configure transition rules to limit who can perform an action.
For example, a product approval transition might be available only to a designated reviewer. A required field could capture the reason for sending a request back to the team.
Rules can help when they solve a real coordination problem. Too many restrictions may slow down routine work, especially when teammates need to move an issue but cannot find an available transition.
Custom statuses and shared workflows
Jira lets administrators configure workflows for different project needs. A custom status can describe a meaningful stage that standard labels do not capture, such as “Waiting for Security Review.”
Before adding a status, ask whether it will change a decision or clarify a handoff. If “Ready” and “Queued” mean the same thing to your team, keeping both may create needless debate.
Shared workflows can make related projects easier to understand. However, a workflow designed for a software team may not fit a marketing project with different approval stages.
Reports, filters, and sprint visibility
Status choices affect how teams interpret boards and reports. If issues remain in “In Progress” during review and testing, a team may not see where work is waiting without more specific statuses.
As a concrete example, a sprint board with separate “Code Review” and “Testing” columns can reveal a queue of work awaiting testers. A single “In Progress” column may conceal that bottleneck.
Keep the reporting question in mind when you design a flow. If the team needs to identify blocked work, a clear “Blocked” status or another reliable signal can make the issue easier to find.
Jira Status Best Practices for Agile Teams
A simple workflow is easier to learn, maintain, and report on. Use these practices to make each status useful in daily team conversations.
- Keep the flow readable. A teammate should understand the board without asking what every column means.
- Use statuses for meaningful states. Add a status when it represents a real stage, handoff, or decision.
- Clarify who owns the next action. If an issue enters “Awaiting Approval,” make clear who is expected to review it.
- Distinguish waiting from active work. A task that is blocked by an external dependency should not look identical to one someone is actively progressing.
- Review status usage with the team. Look for labels that rarely appear, cause repeated questions, or collect work without a clear next step.
- Check status categories and resolution behavior. Confirm that completed issues are categorized and resolved in ways that support your team’s reports.
- Explain the workflow to new teammates. A brief walkthrough with a real issue is often easier to remember than a long list of rules.
The best part? You can improve the workflow gradually. If “Ready for QA” would help the team see a handoff, test it with one workflow before changing every project.
ONES.com Solution: Configurable Workflows for Project Teams

Value proposition
ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is a Jira alternative for managing projects, while ONES Wiki is a Confluence alternative for team knowledge; the products are sold separately.
Core capabilities
- Complex status flows create maintenance work. ONES Project supports custom workflows, giving teams a way to shape issue stages around their process and keep transitions understandable.
- Different work types need different fields. Custom fields let a team capture details relevant to its issues, helping people make decisions with the context they need.
- Sprint progress can be difficult to follow. Sprint management supports Agile planning and execution, giving teams a structured view of work within a sprint.
- Teams need visibility into progress. Built-in reporting helps teams review work without relying on a collection of extra reporting plugins.
- Repeated manual actions take time. Automation can handle routine workflow actions, helping teams reduce repetitive steps.
- Jira users need familiar ways to work. Jira-compatible workflows can make it easier for teams to carry over familiar process patterns as they evaluate a Jira alternative.
- Plugin-heavy setups add complexity. Native project management capabilities can reduce reliance on plugins for common workflow and reporting needs.
- Deployment requirements vary by organization. ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between its cloud and self-hosted versions.
- Teams need room to evaluate the platform. The free plan supports up to 30 seats, which can help a smaller group try the project management capabilities.
Application scenarios
A software team refining review stages: A team can configure stages such as “In Progress,” “Code Review,” and “Testing,” then use sprint management to coordinate its work. Built-in reporting can help the team spot issues waiting at a handoff.
An organization with restricted deployment needs: A group that cannot use a public cloud service can consider On-Premise, Private Cloud, or Air-gapped deployment. Having those choices can support different infrastructure requirements while preserving feature parity with the cloud version.
A team organizing projects and knowledge: A project group can use ONES Project for workflow management and ONES Wiki for team knowledge. Because the products are sold separately, teams can select what fits their needs.
Common Challenges with Jira Statuses
Too many statuses make the board hard to scan
Problem: The board has many near-duplicate labels, and teammates disagree about where an issue belongs.
Solution: Review each status and keep it only when it represents a meaningful stage, handoff, or decision. If “Ready for Work” and “Queued” mean the same thing, combine them or define a clear difference.
Issues get stuck in a status
Problem: Work accumulates in “In Review” or “Testing,” but nobody knows who should act next.
Solution: Clarify the owner of each handoff and agree on what happens when work waits too long. A board column that exposes the queue can help the team discuss capacity.
Completed issues appear in reports incorrectly
Problem: An issue looks finished on the board but does not behave as expected in a report or filter.
Solution: Check the status category, resolution field, and workflow transitions. Make sure the team’s completion path sets the values needed for its reporting approach.
Teams interpret the same status differently
Problem: One person uses “Done” to mean approved, while another uses it for work that is merely coded.
Solution: Agree on entry and exit criteria for important statuses. A short team walkthrough using a real issue can resolve ambiguity before it spreads across projects.
FAQs About Jira Statuses
What is the difference between a Jira status and a Jira workflow?
A Jira status is one stage in an issue’s progress, such as “In Progress” or “Testing.” A workflow is the complete path an issue can follow, including its statuses and the transitions between them. It may also include rules that control who can move an issue or what information is required. Think of a status as a single stop and the workflow as the route connecting the stops.
Can I create custom statuses in Jira?
Yes. Jira administrators can configure statuses to reflect a team’s process. Before adding one, check that it describes a distinct stage with a clear meaning. For example, “Security Review” can help when security approval is a genuine handoff. A label that duplicates “In Review” without changing the next action may make the workflow harder to use.
Can one Jira status appear in more than one board column?
Board configuration determines how statuses are mapped to columns. A board column can group multiple statuses, which helps when a team wants a simpler visual view. The board setup and workflow are related, but they serve different purposes: the workflow defines issue states and transitions, while columns organize the board display.
Why does a Jira issue show as done without a resolution?
An issue’s status and resolution are separate fields. A workflow may move an issue to a completed status without setting a resolution, depending on how the transition is configured. That can affect filters and reports that rely on the resolution field. Review the completion transition and confirm that it updates the fields your team expects.
How many statuses should an Agile team use?
There is no fixed number that works for every team. Start with enough statuses to show meaningful stages, such as planned work, active work, review, testing, and completion. Add a status when it clarifies ownership or exposes a useful handoff. If teammates need frequent explanations to distinguish two labels, simplify the flow or make their meanings clearer.
Conclusion
Jira statuses show where issues stand, while transitions explain how work moves between those stages. Clear names, useful handoffs, and agreed completion criteria make a workflow easier to follow and more useful in reports.
When labels become confusing, start with the team’s actual process and test a smaller, clearer flow. Check how statuses map to board columns, who owns each next action, and whether completed issues behave as expected.
But here's the truth: a workflow only helps when people can use it consistently. Keep your Jira status setup practical, review it as your process changes, and consider a configurable alternative such as ONES Project if your team needs a different way to manage project workflows.