How to Close an Issue in Jira: A Step-by-Step Guide (2026)
Unsure if your Jira issue is truly closed? Learn how to close an issue in Jira, verify its resolution, and fix common blockers. Read now.
You finish the work, click around the Jira issue, and still can’t tell whether it’s actually closed. Maybe the button is missing, the issue remains in a board column, or a report keeps counting it as unresolved.
That uncertainty can create duplicate work and muddy your team’s progress reports. Closing an issue is more than changing its visible status; the workflow may also need to record a resolution.
Here’s how to close an issue in Jira, confirm the change took effect, and troubleshoot common roadblocks. I’ll also explain what to check before closing an issue so you don’t mark unfinished work as complete.
How to Close an Issue in Jira
Open the issue, choose an available workflow transition that completes it, and confirm the issue shows a completed status and resolution. The exact button and status names depend on your Jira project’s workflow.
Open the issue. Find it through your project board, issue search, or a direct link. Check the issue key and summary so you don’t close a similar item by mistake.
Confirm the work is complete. Review acceptance criteria, linked tasks, and any required approvals. For example, a bug might need a fix deployed and verified before it is ready to close.
Look for an available transition. On the issue view, find the status control or workflow action. Jira may show options such as Done, Resolve, or Close, depending on your setup.
Choose the completion transition. Select the option your project uses to finish the work. If Jira asks for a resolution, choose the accurate reason, such as Fixed or Won’t Do.
Complete any required fields. A transition may ask for a comment, resolution, or other project-specific information. Fill in the required fields, then confirm the transition.
Verify the result. Check the status shown on the issue and review its resolution field if available. The issue’s activity history can also show which transition occurred.
But here’s the truth: a status that looks finished does not always mean Jira has recorded the issue as resolved. If reports still count it as open, ask a project administrator to check the workflow and resolution field.
What “Closed” Means in a Jira Workflow
Jira issues move through a workflow made up of statuses and transitions. A status describes the issue’s current stage, while a transition is the action that moves it to another stage.
Your team might use To Do, In Progress, and Done. Another team could use Open, In Review, Resolved, and Closed. These labels aren’t universal; project settings determine what you see.
Resolution is a separate detail that records why work ended, such as Fixed, Duplicate, or Won’t Do. A workflow can set it automatically during a transition, or request it as a required field.
Here’s why: a board may group issues by status, while a report may check whether an issue has a resolution. If those fields disagree, an issue can look complete on the board but still appear unresolved in reporting.
Check These Details Before You Finish an Issue
Take a moment to confirm that the issue is genuinely ready to close. This is especially useful when the task depends on testing, review, or a release that happens outside Jira.
Check that acceptance criteria are complete and any required review has happened.
Confirm linked work is finished, or note why a remaining item does not block closure.
Choose the right resolution if Jira asks for one; don’t mark unfinished work as Fixed.
Add a brief comment when teammates need context, such as the release version or verification result.
Check for duplicate or cancelled work before choosing a resolution other than Fixed.
For example, if a bug fix is ready in a development environment but hasn’t passed testing, leave it in the team’s review or testing stage. Closing it early can make a completion report look better while hiding unfinished work.
Why You Might Not See a Close Option
If there’s no obvious close button, the issue may still be closable through a different transition. The action might appear under the status control, a transition menu, or another location in your Jira interface.
Workflow conditions can also limit who may perform a transition. Your role, project permissions, issue status, or required fields may prevent the action from appearing or completing.
Try this: open the issue’s status menu, check for other completion actions, and look for a message explaining any missing requirement. If no suitable action appears, ask a project administrator to review the workflow and your permissions.
For instance, a team may allow developers to move issues into review but reserve final closure for a tester. In that setup, the missing transition reflects the team’s process rather than a broken issue.
How to Reopen a Closed Jira Issue
If work needs to continue, reopen the issue through the workflow transition intended for that purpose. Depending on the project, the option might be called Reopen, Return to In Progress, or something similar.
When you reopen an issue, check both its new status and its resolution. The workflow should usually clear the resolution when work resumes; if it does not, reports may continue treating the issue as resolved.
Add a comment explaining what changed. For example: “Reopened because the fix did not resolve the login error in the latest test.” That gives teammates a clear reason to pick up the work again.
The best part? A clear reopening note creates a useful history without requiring a separate conversation to explain why the issue returned to active work.
Issue-Tracking Solution: ONES.com
ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.
For teams reviewing how they manage issue workflows, ONES Project offers Jira-compatible workflows, custom fields, sprint management, automation, and built-in reporting. It supports cloud and self-hosted deployment, including air-gapped environments.
Core Capabilities
Issue transitions are hard to control: Configure custom workflows and fields in ONES Project, helping teams match issue stages to their actual review and closure process.
Teams need familiar Jira-style processes: Use Jira-compatible workflows to support a transition for teams that already understand Jira’s issue-management approach.
Reports require too much manual checking: Use built-in reporting to review project progress and issue status in one place.
Sprint work needs clearer coordination: Manage sprints alongside project issues, giving teams a connected view of planned and active work.
Repeated actions take extra effort: Set up automation for routine workflow tasks, reducing manual steps when an issue meets defined conditions.
Teams rely on too many add-ons: Use core project management capabilities together, which can reduce dependence on plugins for common workflows.
Deployment needs vary by organization: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment to fit operational requirements.
Self-hosted teams need consistent capabilities: ONES.com offers feature parity between cloud and self-hosted versions, helping teams keep workflows consistent across deployment choices.
Application Scenarios
Software team managing sprint issues: A team can define how an issue moves from development to review, testing, and completion. Custom fields can capture verification details, while reporting helps the team monitor sprint progress.
Organization with restricted network access: A team that needs an air-gapped environment can run its project management setup in that deployment model. Team members can still use workflows and reporting suited to their issue-management process.
Common Challenges When Closing Jira Issues
The issue looks done but remains unresolved. A status change may not set a resolution. Check the issue details and ask an administrator whether the completion transition should set the resolution automatically.
The close transition is missing. The workflow may not offer it from the current status, or your permissions may restrict access. Ask a project administrator which transition to use and whether you have the required role.
A required field blocks the transition. Read Jira’s prompt and complete the missing information, such as a resolution or comment. If the field is irrelevant, ask an administrator whether the workflow requires it unnecessarily.
A completed issue needs more work. Use the workflow’s reopening transition and explain why the issue is active again. Check that its resolution no longer indicates completion.
FAQs About Closing Jira Issues
Is “Done” the same as “Closed” in Jira?
Not necessarily. Done and Closed are status names that depend on your project’s workflow. A project may use either label, or both at different stages. Check which transition your team expects you to use, and confirm the issue’s resolution when reporting depends on it. The visible status alone may not tell the whole story.
Why can’t I close an issue in Jira?
The current workflow may not offer a completion transition from the issue’s status. Your permissions or project role could also restrict that action, or Jira may require fields you haven’t completed. Check for a message on the issue and look through the available status actions. If you still can’t proceed, ask a project administrator to review the workflow and your access.
Can I close an issue without setting a resolution?
That depends on the workflow. Some projects set the resolution automatically when you complete a transition, while others require you to choose one. In some configurations, an issue can reach a completed status without a resolution. If reports still treat it as unresolved, ask an administrator to check whether the transition sets the correct resolution.
How do I reopen a closed Jira issue?
Open the issue and choose the available transition that returns it to active work. The action might be called Reopen or have another project-specific name. Add a comment explaining why the issue needs attention again. After the transition, verify the status and resolution so the issue no longer appears completed in reports.
Conclusion
To close a Jira issue, confirm the work is complete, choose the right workflow transition, and verify both the status and resolution. If the action is missing or blocked, check for required fields and ask an administrator about workflow rules or permissions.
A careful closure prevents unfinished work from disappearing into completion reports. When you make the final status clear and leave useful context, teammates can trust the issue history and understand what happens next.