Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Learn how to set up, customize, and manage Jira Cloud projects.
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
Learn more on how you can set up Jira Cloud for your team.
Issues track the work your team needs to get done to progress your projects and your goals. Each issue collects and displays the information your team needs to collaborate into a set of fields. An issue's status, priority, and resolution represent some of the most important fields describing and reporting on your team's work. They give your team at-a-glance information about where the work is in your workflow, how important it is to your project goals, and a description of how the work was completed.
This page lists the default statuses, priorities and resolutions that come with your Jira products. Jira admins: learn more about creating your own statuses, priorities, or resolutions.
An issue's status indicates its current place in the project's workflow. Default statuses are created when you create a project from one of our templates. The statuses are recommended starting points for each template, but you can edit or remove them from a workflow to suit your team's need. You can also create your own. Learn more about configuring statuses and their descriptions.
Here's a list of the statuses that come with JIRA products, depending on what projects you've created on your site.
The issue is open and ready for the assignee to start work on it.
This issue is being actively worked on at the moment by the assignee.
Work has finished on the issue.
The issue has been reported and is waiting for the team to action it.
The assignee has carried out the work needed on the issue, and it needs peer review before being considered done.
A reviewer is currently assessing the work completed on the issue before considering it done.
A reviewer has approved the work completed on the issue and the issue is considered done.
Work has stopped on the issue and the issue is considered done.
A reviewer has rejected the work completed on the issue and the issue is considered done.
For content management and document approval projects, the work described on the issue is being prepared for review and is considered in progress, in the draft stage of writing.
For content management projects, the work described on the issue has been published and/or released for internal consumption. The issue is considered done.
For recruitment projects, this indicates that the candidate is currently in the interviewing stage of the hiring process.
For recruitment projects, this indicates that the candidate has completed interviewing and interviewers are discussing their next steps in the hiring process.
For recruitment projects, this indicates that the candidate has applied and is being considered for interviews.
For recruitment projects, this indicates that the candidate has been offered a position and recruiters are working to shore up the details.
For recruitment projects, this indicates that the candidate has accepted the position. The issue is considered done.
For recruitment projects, this indicates that a candidate has applied and recruiters are waiting to screen them for future action in the hiring process.
For document approval projects, the work described on the issue has passed its initial review and is being closely proofed for publication.
For lead tracking projects, this indicates that the lead was unsuccessful. The issue is considered done.
For lead tracking projects, this indicates that the lead was successful. The issue is considered done.
For lead tracking projects, this indicates that the sales representative has contacted their lead and the pitch is in progress.
For lead tracking projects, this indicates that the sales team has identified and opportunity they want to pursue.
For lead tracking projects, this indicates that the sales team is adjusting their terms to make a sale.
For procurement projects, this indicates that the service or item was purchased. The issue is considered done.
For procurement projects, this indicates that the service or item has been requested and is waiting for a procurement team member to action the request.
Jira Software statuses
If you have Jira Software, you also get these statuses by default, depending on what projects you've created on your site:
This issue was once resolved, but the resolution was deemed incorrect. From here, issues are either marked assigned or resolved.
A resolution has been taken, and it is awaiting verification by reporter. From here, issues are either reopened, or are closed.
The issue is considered finished. The resolution is correct. Issues which are closed can be reopened.
Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
The source code committed for this issue has possibly broken the build.
The issue is waiting to be picked up in a future sprint.
Selected for Development
The issue is verified and has been selected to be worked on in the future.
Jira Service Management statuses
If you have Jira Service Management, you also get these statuses by default, depending on what projects you've created on your site:
Waiting for support
Waiting for customer
Waiting for approval
Awaiting CAB approval
Peer review / change manager approval
Work in progress
An issue's priority indicates its relative importance. The default priorities are listed below. Both the priorities and their meanings can be customized by your administrator to suit your organization. Learn more about configuring priorities and their descriptions.
This problem will block progress.
Serious problem that could block progress.
Has the potential to affect progress.
Minor problem or easily worked around.
Trivial problem with little or no impact on progress.
An issue can be completed, or resolved, in many ways. An issue resolution is usually set when the status is changed. Your administrator may have customized these to suit your organization. Learn more about configuring resolutions and their descriptions.
Once an issue is resolved (that is, the issue's Resolution field is filled in), references to that issue show the key in strikethrough text.
Here's the issues resolutions that come with your Jira products by default:
Work has been completed on this issue.
This issue won't be actioned.
The problem is a duplicate of an existing issue.
Jira Software resolutions
If you have Jira Software, you also get these resolutions by default:
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
Jira Service Management resolutions
If you have Jira Service Management you also get these resolutions by default:
The problem has a documented root cause and a work around.
Was this helpful?