How to Close a Jira Ticket: 7 Steps and a Quick Checklist
Is your Jira ticket still open after the work is done? Learn how to close the Jira ticket in 7 steps with a quick checklist. Read now.
A Jira ticket can look finished while its status, resolution, or acceptance checks still say otherwise. Close it too early, and teammates may miss unfinished work; leave it open, and completed work can clutter boards and reports.
That uncertainty often comes from different workflows, custom statuses, and team habits. A “Done” column does not always mean a ticket is formally closed, and the available transition can vary between projects.
But here's the truth: you can close a Jira ticket reliably by checking its acceptance criteria, confirming the right workflow transition, and verifying the final status. Use the seven steps and quick checklist below to finish tickets clearly, avoid accidental closures, and give your team an accurate record of what’s complete.
How to Close a Jira Ticket in 7 Steps
To close a Jira ticket, confirm the work is complete, check its details, then use the project’s closing transition and verify the resulting status. These steps work across many Jira setups, though button names and workflow rules can differ.
-
Open the correct issue. Search by issue key, such as APP-248, or find the ticket on your board. Check the project and summary before changing anything, especially when several similar issues appear in search.
-
Review the acceptance criteria. Confirm each requirement has been met and that any promised testing is complete. For example, if a ticket requires a confirmation message after saving, test that specific interaction rather than relying on a general “works for me.”
-
Check linked work and dependencies. Look for related subtasks, blockers, or follow-up issues. A feature ticket may be ready to close while a separate enhancement remains open; make sure the remaining work is tracked clearly instead of silently disappearing.
-
Update the ticket details. Add a concise completion note and any relevant test result. Fill in required fields, such as resolution or release information, when your workflow asks for them. Avoid adding sensitive details that do not belong in the issue.
-
Choose the correct workflow transition. Select the button or menu action that moves the ticket to its final status. Depending on your Jira configuration, it may say “Close,” “Resolve,” “Done,” or something specific to your team.
-
Complete any transition prompts. Jira may ask you to select a resolution, enter a comment, or confirm another required field. Read each prompt and choose the value that reflects the actual outcome; do not select “Fixed” if the issue was closed as a duplicate.
-
Verify the final state. Check the status and resolution after the transition. Make sure the ticket no longer appears as active work on the board, and confirm any required follow-up issue remains visible and assigned.

Quick checklist before closing
Acceptance criteria and promised testing are complete.
Related blockers, subtasks, and follow-up work are accounted for.
Required fields and the completion note are accurate.
The closing transition matches the team’s workflow.
The final status and resolution reflect the outcome.
Understand the Difference Between “Done,” “Resolved,” and “Closed”
Jira status names are configurable, so “Done” does not necessarily mean the same thing in every project. A team may use “Resolved” when work is complete but still awaiting verification, then move the ticket to “Closed” after review.
Here's why: Jira workflows determine which statuses and transitions are available. One project might have a single “Done” status, while another separates implementation, testing, resolution, and closure.
For example, a support team may resolve a reported defect after applying a fix, then close it after the requester confirms the result. A software team may close a completed task directly once its acceptance checks pass.
Check Resolution and Required Fields
Status and resolution are related, but they serve different purposes. Status shows where an issue sits in its workflow; resolution records how the issue ended, such as fixed, duplicate, or won’t fix.
If a ticket moves to a completed status but its resolution remains empty, reports may treat it as unresolved. Your project may populate the resolution automatically, or Jira may ask you to select one during the transition.
For instance, when closing a duplicate bug, link it to the original issue and choose the resolution that reflects the duplicate outcome. That gives teammates a clear history and helps avoid counting the same defect twice.
What to Do When You Can’t Close a Ticket
If the close action is missing, first check whether the ticket is in a status that allows the transition. Some workflows permit closure only after review, testing, or approval.
You might be wondering: what if the transition appears but Jira rejects the change? Look for a missing required field or a validation message. A workflow rule may require an assignee, resolution, comment, or completed subtask before the ticket can move forward.
If the issue still cannot close, ask a project administrator to review your permissions and workflow. Share the ticket key and the exact message you see; that gives them a practical starting point without changing the workflow blindly.
Reopen a Ticket When the Work Isn’t Actually Complete
Closing a ticket is not always the last word. If testing reveals the same defect or the requested outcome is missing, use the workflow’s reopen or return transition when available.
Let me explain: a clear reopening note helps the next person understand what failed. For example, write, “Reopened: the save confirmation still does not appear in Firefox 124,” rather than adding only “Still broken.”
If the original ticket should stay closed, create or link a new issue for separate follow-up work. That preserves the original outcome while making the new task visible, assigned, and measurable.
Closing Work Clearly in ONES.com
When your team wants project work and team knowledge in one environment, ONES.com offers 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.

ONES Project supports Jira-compatible workflows, sprint management, custom workflows and fields, automation, and built-in reporting. These capabilities can help teams make completion rules more visible, reduce reliance on plugins, and keep project work organized.
Core capabilities
Unclear closing rules → Jira-compatible workflows → Set up familiar workflow patterns so team members can follow recognizable stages and transitions.
Different teams need different review steps → Custom workflows → Configure transitions around your team’s approval and completion process.
Inconsistent ticket details → Custom fields → Capture the information your team needs to review work before closing it.
Hard-to-track sprint work → Sprint management → Organize tasks by sprint and review unfinished work before marking a sprint item complete.
Manual status updates → Automation → Automate eligible actions, reducing repetitive updates when defined conditions are met.
Limited progress visibility → Built-in reporting → Review project progress and identify work that remains open or needs attention.
Separate project and knowledge needs → ONES Project and ONES Wiki → Use the project management or knowledge management product that fits your needs; each is available separately.
Deployment constraints → Cloud, On-Premise, Private Cloud, or Air-gapped deployment → Choose an environment suited to your organization’s hosting and security requirements.
ONES.com provides feature parity between its cloud and self-hosted versions. That lets teams consider deployment requirements without giving up the platform’s feature set.
Application scenarios
A software team closing sprint work: A team can use custom fields to record test results and a workflow transition to distinguish review from completion. Built-in reporting can help the team spot tickets that remain unfinished at sprint end.
A restricted-network project team: An organization that needs an air-gapped environment can choose that deployment option and configure workflows for its internal review process. ONES Project can support project tracking, while ONES Wiki can serve knowledge management if the team needs both products.
Common Challenges When Closing Jira Tickets
The close action is unavailable. The ticket may be in the wrong status, you may lack permission, or a workflow condition may not be met. Check the current status and any message Jira displays, then ask a project administrator if the transition remains unavailable.
The ticket closes without a clear outcome. A missing completion note or inaccurate resolution leaves teammates guessing. Add a short summary of what changed and select the resolution that matches the result.
Related work gets overlooked. A parent ticket can look complete while a subtask or blocker remains open. Review linked issues and either finish them or clearly assign and track the remaining work.
A completed ticket needs to be reopened. Reopen it through the correct workflow transition and explain what failed. If the new work is separate, create and link another issue so the original completion history stays clear.
FAQs About Closing Jira Tickets
Is closing a Jira ticket the same as resolving it?
Not always. Jira workflows can use “Resolve” and “Close” as separate statuses, or use only one completed status. Resolution is an outcome value, such as fixed or duplicate, while status shows the issue’s workflow position. Check your project’s workflow and verify both fields after the transition. If your team has a defined closure policy, follow that process consistently.
Why can’t I see the Close button in Jira?
The ticket’s current status may not allow a direct close transition, or your account may not have permission to make that change. A workflow rule could also require approval, testing, or specific fields first. Check the issue’s available actions and any warning Jira displays. If the action is still missing, ask a project administrator to review the workflow and your permissions.
Should I close a ticket if a related task is still open?
It depends on whether the remaining task blocks the outcome described in the ticket. If it does, keep the ticket open or follow your team’s process for blocked work. If it is separate follow-up work, create or link another issue and make its owner clear. For example, a completed bug fix can close while a later enhancement remains tracked as a separate ticket.
Can I reopen a Jira ticket after closing it?
Often, yes, if the project workflow includes a reopen or return transition and you have permission to use it. Reopen the issue when the original outcome is incomplete or fails verification, then add a brief explanation and any useful test details. If the new work is distinct, a separate linked issue may be clearer. Your project’s workflow determines which option is available.
Conclusion
Close a Jira ticket only after checking its acceptance criteria, related work, required fields, and final workflow state. A short completion note and the correct resolution help teammates understand what happened without reopening old questions.
When the close action is missing, check the workflow and permissions instead of guessing. And if later testing shows the work is incomplete, reopen the issue with a clear explanation or track separate follow-up work in a linked ticket.
That small pause before closure prevents inaccurate boards and confusing reports. Use the seven-step process and checklist to make every completed ticket easier to trust.