How to Close a Jira Issue: 6 Steps and Final Checks to Run
Not sure when a Jira issue is truly done? Learn how to close a Jira issue with 6 steps and final checks. Read now to close it confidently.
A Jira issue can look finished while its workflow still says “In Progress,” or it can show “Done” with no resolution recorded. Either way, your team may struggle to tell whether the work is truly complete.
That uncertainty can affect reports, sprint totals, handoffs, and the next person trying to understand what happened. Closing too early can hide unfinished testing or dependent work; waiting too long leaves completed work cluttering active queues.
But here's the truth: closing an issue is a workflow transition, not just a status change. Follow six checks to move it into the right final state, confirm its resolution, and leave a useful record for your team.
How to close a Jira issue in 6 steps
To close a Jira issue, open it, confirm the work and related tasks are complete, run the available workflow transition, then verify its status and resolution. The exact button labels depend on your Jira project’s workflow and permissions.
Open the issue and confirm its identity. Check the issue key, title, and project before making changes. For example, if you are closing APP-248, make sure it is the login defect you resolved—not a similarly named follow-up task.
Confirm the work is actually complete. Review the acceptance criteria, test results, and any required review. If the issue describes a bug fix, verify the reported behavior no longer occurs and that the change has reached the required environment.
Check subtasks and dependencies. Make sure required subtasks are complete and linked blockers have been addressed. A parent issue may be ready to close only after its testing or review task is finished, depending on your team’s rules.
Add a completion comment if it helps the next person. State what changed and how you verified it. For instance: “Fixed the session timeout; confirmed the user remains signed in after refreshing.” Keep sensitive details out of public comments.
Choose the appropriate workflow transition. Select the status control or transition action shown on the issue. Depending on your workflow, the action might be called “Done,” “Close,” “Resolve,” or something specific to your team. Complete any required fields or prompts.
Verify the final status and resolution. Confirm the issue appears in the intended completed status. If your project displays a resolution field, check that it reflects the outcome, such as “Fixed,” “Won’t Do,” or “Duplicate.”
Here's why that final check matters: a status and a resolution are related, but they are not always the same field. Your workflow may update both automatically, or it may require a specific transition to set the resolution.

Jira status and resolution mean different things
A status shows where an issue sits in the workflow, such as “To Do,” “In Progress,” or “Done.” Resolution records why the issue is considered complete. Common resolution values include “Fixed,” “Won’t Do,” and “Duplicate.”
For example, two issues may both reach “Done,” while one was fixed and the other was closed as a duplicate. That distinction helps teams understand outcomes and keep reports meaningful. If the resolution remains empty, a completed issue may still appear unresolved in some Jira views or reports.
Let me explain: your workflow controls when these fields change. If a completed issue has the wrong resolution, ask your Jira administrator to review the transition and field configuration rather than repeatedly changing the status.
Final checks to run before closing
Use a short review before you move an issue into its final state. The right checks depend on the work, but a few practical questions catch common oversights.
Does the issue meet its acceptance criteria?
Have required testing, review, or approval steps finished?
Are its subtasks complete, or clearly assigned to a separate follow-up?
Have blocking links or related issues been reviewed?
Does the completion comment explain the outcome clearly?
Will the selected resolution accurately describe what happened?
For example, a feature may be coded and reviewed but still await deployment. If your team considers deployment part of completion, keep the issue open until the release is verified. If deployment is tracked separately, close the feature and link the release task.
The best part? This check does not need to become a long meeting. A quick review against the issue’s acceptance criteria can be enough for a small task, while a production change may need test and release confirmation.
Why the close action can look different in each Jira project
Jira projects can use different workflows, so there is no single close button that appears everywhere. One project may offer a “Close” transition; another may move issues from “In Review” to “Done.” Your available actions can also depend on permissions.
If you cannot see the expected transition, check whether the issue is in a status that allows it. A workflow may require another step first, such as review or testing. You may also lack permission to perform that transition.
You might be wondering: should you change the status directly? Use the workflow transition when one is available. It can apply required fields and workflow rules that a simple status edit may not trigger.
What to do if you close an issue by mistake
If an issue was closed too early, look for a reopen or return-to-work transition. Your project might label it “Reopen,” “Reopened,” or “In Progress.” Add a comment explaining what remains unfinished so the next assignee has context.
Then check the resolution. Some workflows clear it when an issue is reopened; others may require a Jira administrator to correct it. Leaving a stale resolution in place can make the issue appear complete in reports even though work has resumed.
For instance, if testing reveals a new defect after closure, reopen the original issue only when the remaining work belongs to its scope. If it is a separate problem, create a linked issue and describe the relationship clearly.
How teams can make issue closure more consistent
Agree on what “complete” means for common work. A bug fix might require verification in a test environment, while a research task might be complete once findings are shared with the team. Clear criteria reduce debates at the end of a sprint.
Keep transition names and resolution choices understandable. If team members routinely confuse “Resolved” with “Closed,” ask your Jira administrator whether the workflow can better reflect your actual process. A short team guide with examples can help new teammates make consistent choices.
For example, your team could agree that “Fixed” means the behavior was corrected and verified, while “Won’t Do” means the team intentionally chose not to make the change. Those definitions make reports easier to interpret later.
ONES.com solution for teams managing issue workflows
ONES.com brings project management and knowledge management together on a unified platform. ONES Project is a Jira alternative for teams that want configurable issue workflows, while ONES Wiki is a Confluence alternative for team knowledge. The products are sold separately.

For teams reviewing how they manage issue work, ONES Project offers Jira-compatible workflows, sprint management, custom fields, automation, and built-in reporting. These capabilities can help teams shape their process while reducing reliance on plugins for common project management needs.
Core capabilities
Workflows that vary by team: When one process does not fit every project, custom workflows let teams define appropriate issue stages and transitions. Jira-compatible workflows can make the switch more familiar for teams moving from Jira.
Custom fields for useful context: When teams need details beyond a basic issue description, custom fields capture the information relevant to their work. That can make handoffs and issue reviews clearer.
Sprint management: When teams plan work in iterations, sprint management supports planning and progress tracking. The result is a clearer view of what is active and what remains.
Built-in reporting: When project leads need to understand progress, built-in reporting provides project visibility without requiring a separate reporting plugin for every common need.
Automation: When repetitive workflow actions consume time, automation can handle configured routine steps. Teams can focus more attention on decisions that need human review.
Deployment choice: When infrastructure or security requirements shape where work is hosted, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. The self-hosted version has feature parity with the cloud version.
Related team knowledge: When procedures or project guidance need a dedicated home, ONES Wiki provides knowledge management as a separate product. Teams can choose it when that capability fits their needs.
Free access for smaller teams: When a team wants to evaluate the platform, the free plan supports up to 30 seats. That gives a small group room to try project workflows before deciding what fits.
Application scenarios
A software team could use ONES Project to define a workflow that moves a defect through development, review, testing, and completion. Custom fields could capture test details, while reporting gives the team a view of outstanding work.
A team with restricted network requirements could consider an On-Premise, Private Cloud, or Air-gapped deployment. Another group might use ONES Wiki separately to maintain internal process guidance alongside its project management setup.
Common challenges when closing Jira issues
The issue shows “Done,” but reports still count it as unresolved. The resolution may be empty or incorrect. Check the resolution field and ask your Jira administrator to review the workflow if it does not update during the expected transition.
The close transition is missing. The issue may need to pass through another workflow stage, or your account may not have the required permission. Check the current status and contact your Jira administrator if the transition should be available.
A parent issue closes while subtasks remain active. Review the child tasks before closing the parent. If the remaining work is intentionally separate, create or retain a clear link and explain the handoff in a comment.
Different teammates choose different resolutions. Agree on simple definitions for choices such as “Fixed,” “Duplicate,” and “Won’t Do.” Share examples so team members can select a resolution that reflects the actual outcome.
An issue needs work after closure. Use the appropriate reopen transition when the unfinished work belongs to the same issue. If it is a distinct problem, create a linked issue and clarify why the work is connected.
FAQs about closing Jira issues
What is the difference between resolving and closing an issue?
The terms depend on your Jira workflow. “Resolved” often marks work as complete while leaving room for verification or reopening, whereas “Closed” may represent the final workflow state. Your project might use both statuses, only one, or different labels. Check the workflow used by your project and confirm the resolution value before treating the issue as finished.
Can I close a Jira issue without setting a resolution?
Some configurations may allow a completed status with no resolution, but that can cause confusing reports or unresolved counts. Many workflows set the resolution automatically during a transition. If the value stays empty, check whether you used the intended transition and ask a Jira administrator to review the workflow configuration.
Why can’t I close an issue in Jira?
The issue may be in a status that does not allow a direct close transition, or your account may not have permission. The workflow might require a review, test, or approval step first. Check the current status and available actions. If you believe the action should be available, ask your Jira administrator to confirm the workflow and permissions.
How do I reopen a closed Jira issue?
Open the issue and look for a transition such as “Reopen” or “In Progress.” The label depends on your project’s workflow. Add a comment describing what remains to be done, then check whether the resolution was cleared. If no reopening action appears, contact your Jira administrator or create a linked issue when the work is separate.
Should I close a duplicate Jira issue?
If the issue genuinely duplicates another, use the resolution your team assigns to duplicates, if available. Link it to the primary issue and leave a brief comment explaining where the work will continue. This preserves context and helps prevent someone from treating the duplicate as an independent task later.
Conclusion
Closing an issue well means confirming the work, checking subtasks and dependencies, using the right workflow transition, and verifying the final resolution. Those small steps help prevent unfinished tasks from disappearing into completed queues.
If Jira does not offer the transition you expect, check the workflow and permissions rather than guessing. A clear team definition of “complete” can make issue closure more reliable and keep project reporting useful.
But here's the truth: the final click is only one part of a clean handoff. Leave a concise record, confirm the issue’s final state, and choose a workflow that reflects how your team actually finishes work.