How to Close an Issue in Jira: Step-by-Step Guide for Teams
Need to know how to close the issue in Jira? Follow the right workflow steps to update status and keep reports accurate. Read now.
A Jira issue can appear finished while still sitting in an active status, leaving your board and reports out of sync. That small mismatch can create confusing sprint totals, repeated follow-ups, and uncertainty about who still needs to act.
Closing an issue is not always as simple as clicking “Done.” Your project’s workflow may require a specific transition, a resolution value, or a final review before the issue can close.
But here's the truth: the right process is straightforward once you know which status transition your team expects. I’ll walk you through closing an issue, checking that Jira recorded the resolution, and handling common snags so your team can finish work with confidence.
How to close a Jira issue correctly
Open the issue, use an available workflow transition to move it to the team’s completed status, and confirm Jira records the resolution. The exact button or status name can differ between projects.
Open the issue. Find it through your Jira project, board, or issue search. Check the issue key and summary so you do not close a similar item by mistake.
Review the completion criteria. Confirm that the work is finished, required review is complete, and any linked tasks or acceptance criteria have been addressed. For example, a bug might need a verified fix before it can close.
Start the correct transition. On the issue view, look for a transition button such as “Done,” “Close,” or “Resolve.” In some Jira layouts, you can choose a destination status from the current status menu.
Complete any required fields. Jira may ask you to add a resolution, closing note, or other project-specific details. Enter accurate information before submitting the transition.
Confirm the new status. Check the issue’s status after the transition. If your workflow uses a separate resolution field, verify that it now has the appropriate value, such as “Fixed” or “Won’t Do.”
Reopen the issue if the work returns. Use the available reopen transition rather than changing unrelated fields. This helps your team distinguish active work from completed work.
Here's why: Jira workflows control which transitions are available. If you cannot see a close or completion option, the issue may need another status first, or your account may lack permission.

Understand statuses and resolutions before closing
A status describes where an issue sits in its workflow, such as “In Progress,” “Review,” or “Done.” A resolution records why the issue is considered complete, such as “Fixed,” “Duplicate,” or “Won’t Do.” Projects can configure these fields differently.
For example, a team might move a bug to “Done” after testing, then set its resolution to “Fixed.” Another team could close a duplicate as “Won’t Do.” The status communicates progress; the resolution gives more context about the outcome.
Some Jira workflows set the resolution automatically during a transition. Others ask you to choose one. If a completed issue still appears unresolved in reports, check the resolution field and ask your Jira administrator whether the workflow sets it correctly.
Choose the right completion status for your project
Jira projects do not always use the same wording. One team may finish work in “Done,” while another uses “Closed,” “Resolved,” or a custom status such as “Released.” Follow the project’s workflow rather than assuming one label applies everywhere.
Imagine a software team with statuses for development, review, testing, and release. A developer may finish a code change, but the issue should remain open until testing passes. Moving it to the final status too early can make the board look healthier than the work really is.
You might be wondering: should you choose “Resolved” or “Closed”? Check your team’s workflow and reporting rules. In some projects, “Resolved” means the work is complete but still needs confirmation; “Closed” may be the final state.
What to do when Jira will not let you close an issue
If the transition is missing or fails, check the issue’s current status first. A workflow may require you to move through an intermediate stage, such as “Ready for Review,” before selecting “Done.” Follow the visible workflow path.
Jira can also require fields before a transition succeeds. A bug might need a resolution, while a change request could require a closing comment. If Jira highlights a field or displays an error, complete the requested information and try again.
Still stuck? Confirm that you have permission to transition the issue. If the problem affects multiple issues or teammates, ask a Jira administrator to review the workflow conditions, transition rules, and project permissions.
Keep issue closures reliable across the team
Agree on what “complete” means before closing work. For a support team, that might mean the customer received an answer. For a development team, it could mean code passed review and testing.
Use a short closing note when the outcome is not obvious. For example, “Closed as duplicate of PROJ-184; the fix is tracked there” gives the next person useful context without making them investigate both issues.
The best part? A consistent closure habit improves more than board appearance. Accurate status and resolution details help teams review completed work, understand recurring outcomes, and spot issues that were closed prematurely.
Jira issue-closure workflows with ONES.com

Value proposition
ONES.com brings project management and knowledge management together on a platform powered by ONES Assistant. ONES Project is the project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.
For teams reviewing their issue workflow, ONES Project offers configurable statuses, transitions, and reporting. You can shape a closure process around your team’s review requirements, including teams that need on-premise or air-gapped deployment.
Core capabilities
Pain: Teams need a familiar transition-based workflow. ONES capability: Jira-compatible workflows. Result: Teams can map familiar issue stages into their project process.
Pain: Fixed fields do not capture the details a team needs at closure. ONES capability: Custom fields and workflows. Result: You can request relevant completion details as issues move through the process.
Pain: Teams struggle to see issue outcomes. ONES capability: Built-in reporting. Result: Project leads can review progress without relying on a collection of add-ons.
Pain: Sprint work needs a clear finish point. ONES capability: Sprint management. Result: Teams can coordinate issue completion within planned iterations.
Pain: Repetitive actions make handoffs inconsistent. ONES capability: Automation. Result: Teams can reduce manual steps in recurring workflow tasks.
Pain: A project may depend on many plugins. ONES capability: Native project features and reporting. Result: Teams may be able to reduce plugin reliance for common project needs.
Pain: Some organizations cannot run project work in a public cloud. ONES capability: Cloud, on-premise, private cloud, and air-gapped deployments. Result: You can evaluate deployment options that fit operational requirements.
Pain: Self-hosted teams worry about feature gaps. ONES capability: Feature parity between cloud and self-hosted versions. Result: Teams can assess deployment choices without planning around a reduced feature set.
ONES.com offers a free plan for up to 30 seats. Its deployment options include cloud and self-hosted setups, including air-gapped environments. You can assess the workflow and deployment fit before deciding whether it suits your team.
Application scenarios
Software teams: A team can require review and testing before an issue reaches its final status. Custom transitions can reflect those checks, while reporting helps leads review completed work.
Restricted environments: An organization that needs on-premise or air-gapped deployment can evaluate ONES Project as a Jira alternative while configuring issue workflows for its operating requirements.
Common challenges when closing Jira issues
The close transition is missing. The issue may be in a status that does not allow direct closure, or your account may lack permission. Check the workflow path and ask a project administrator to review access if needed.
The issue looks complete but remains unresolved. A resolution may not have been set during the transition. Check the resolution field and ask an administrator whether the workflow should populate it automatically.
A completed issue was closed too early. Reopen it using the project’s workflow transition, then move it forward after the required work is complete. A clear team definition of “done” can prevent repeat mistakes.
Reports show confusing completion totals. Different teams may use different final statuses or resolution values. Agree on shared meanings, then check that reports include the statuses your team considers complete.
FAQs about closing Jira issues
What is the difference between resolving and closing an issue in Jira?
Jira uses workflows configured for each project, so the distinction depends on your setup. “Resolved” may mean the work is complete but awaiting verification, while “Closed” may represent the final state. A resolution field can separately record why the issue is complete. Check your project’s workflow and team conventions before choosing a transition.
Why can’t I see a Close button in Jira?
The workflow may not offer a direct transition from the issue’s current status. You may need to move it through another stage first, such as review or testing. The option can also be hidden because of project permissions or workflow conditions. Check the current status and available transitions, then contact a Jira administrator if the expected path is unavailable.
Can I reopen a closed Jira issue?
Often, yes, if the project workflow includes a reopen transition and you have permission to use it. Open the issue and look for a transition such as “Reopen” or “Return to In Progress.” If it is missing, ask a project administrator about the workflow. Reopening is clearer than changing unrelated fields because it records that the work has become active again.
Should I add a comment before closing an issue?
Add a comment when the outcome needs context, especially if someone may need to understand the decision later. For example, explain that a request was closed as a duplicate and identify the issue where work continues. Your project may also require a comment during the closing transition. Keep the note brief, specific, and useful to the next person reviewing the issue.
Close issues with a clear finish
Closing an issue means more than changing a label. Check that the work meets your team’s completion criteria, use the right workflow transition, and confirm the status and resolution afterward.
When Jira blocks the transition, look for a required workflow stage, missing field, or permission issue. A brief closing note can also prevent confusion when teammates revisit the issue later.
That small routine helps prevent the frustration of work that looks finished but remains open or unresolved. Use the same approach across your team, and your Jira issues will give a clearer picture of what is complete and what still needs attention.