How to Close Tickets in Jira: Steps, Checks, and Examples
Unsure how to close ticket in Jira correctly? Learn the steps, checks, and examples for a reliable close. Click to discover how.
Closing a Jira ticket can look like one quick status change. But if you close it before confirming the fix, linking the right work, or checking the workflow, the issue may reopen or disappear from the team’s active view.
That creates extra back-and-forth: someone reports the same problem again, a reviewer asks what happened, and your team has to retrace its steps. Jira workflows can also use different status names and transition rules, so the button you expect may not be available.
Here’s the truth: a reliable close starts with checking the issue and ends with confirming its final status. Follow the steps below to close a Jira ticket cleanly, handle common exceptions, and make sure the result is clear to everyone who needs it.
How to Close a Ticket in Jira
To close a Jira ticket, open the issue, confirm its work is complete, add a useful resolution note, and select the workflow transition that moves it to a closed status. Then verify the final status and resolution fields.
Jira projects can customize workflows, so your transition might be labeled Close, Resolve, or Done. Use the transition that matches your team’s process rather than assuming every project has the same buttons.
- Open the issue you want to close. Use the issue key, such as
APP-248, or find it through the project’s issue search. Check that the summary and project match the ticket you intend to finish.
- Confirm that the work is complete. Review the latest comments, linked tasks, and acceptance criteria. If the fix needs testing or review, complete that work before moving the ticket into a final status.
- Add a closing note. Explain what changed, how the result was checked, and any follow-up that remains. For example: “Updated the export permission; verified the report downloads for an analyst account.”
- Choose the correct workflow transition. Select Close, Resolve, Done, or the transition your project provides. If Jira requests a resolution, choose the option that accurately describes the outcome.
- Complete any required transition fields. Add a resolution, closure reason, or other required detail. If a field is missing, Jira may prevent the transition until you fill it in.
- Verify the final state. Check the status shown on the issue and confirm that its resolution reflects the outcome. If the ticket still appears active, it may have moved to a non-final status instead.

Check that the issue is ready
Before changing the status, compare the ticket with its acceptance criteria. A login bug, for example, may need confirmation on both desktop and mobile if the issue describes both experiences.
Check linked work as well. If the ticket depends on an unfinished review or a related task, closing it could give teammates the wrong impression about what is ready.
Write a useful closing note
A strong note gives the next person enough context to understand the result without asking you to explain it. Mention the change and the verification you completed.
For a defect, you might write: “Fixed the duplicate invoice alert and checked that a single alert appears after payment.” For a request that was declined, state the decision and its reason.
Use the right transition and resolution
A Jira status describes where an issue sits in the workflow. A resolution records how the issue ended. Depending on your project’s setup, moving a ticket to a status called Done may not automatically set its resolution.
When Jira presents a resolution field, select a value that matches the outcome. For example, a completed change may be resolved as Fixed, while a duplicate report may use Duplicate.
What Jira’s Closed Status Means
A closed status usually signals that the team considers work on an issue finished. The exact meaning depends on the project’s workflow, so check how your team distinguishes Resolved, Done, and Closed.
For example, a support team may use Resolved when a fix is ready and Closed after the requester confirms it works. A software team might use Done once development and review are complete.
Here’s why the distinction matters: reports and filters may use status, resolution, or both. If a ticket has a final-looking status but no resolution, it might still appear in an unresolved issue search.
Ask your Jira administrator or team lead if the status meanings are unclear. A short explanation of the local workflow can prevent inconsistent closures across a project.
Checks to Make Before Closing an Issue
A quick final review can prevent premature closure. Think of it as a handoff: the issue should tell someone else what changed and whether the result was checked.
- Acceptance criteria: Confirm each stated requirement has been met, including any relevant edge cases.
- Testing or review: Record the check that supports completion, such as a successful test or reviewer approval.
- Related work: Verify linked tasks or blockers are complete, or explain why they do not prevent closure.
- Resolution: Select a value that accurately describes the outcome when Jira requires one.
- Follow-up: Create a separate issue for future work instead of leaving an unclear promise in the closing note.
For instance, if a ticket asks for a new billing alert, confirm that the alert appears in the intended situation. If testing covered only one payment method, say so clearly rather than implying broader verification.
The best part? These checks do not need to become a long ceremony. A few focused questions can catch missing work before the ticket leaves the team’s active queue.
Examples of Closing Different Jira Tickets
The right closure note depends on the kind of issue and how it was handled. Keep the message specific enough to explain the outcome, while avoiding details that belong in a separate follow-up issue.
Closing a fixed bug
Example: “Corrected the date shown in the order summary. Checked orders created in both time zones, and the displayed date now matches the order record.”
This note names the change and describes the check. If the fix needs a release before customers can see it, follow your team’s workflow for marking the work complete or waiting for deployment.
Closing a duplicate report
Example: “Closing as a duplicate of APP-193. The earlier issue tracks the same checkout error and contains the current investigation.”
Link the related issue and explain the relationship. That gives teammates a clear path to the active investigation instead of leaving them to search for it.
Closing a request that will not proceed
Example: “Closing this request because the team will keep the current approval rule. The reason is that the proposed change would bypass the required review.”
State the decision and its rationale respectfully. If the requester needs another option, suggest the appropriate next step or create a follow-up issue when your team agrees.
When Jira Won’t Let You Close a Ticket
If Jira blocks the transition, read the message beside the status control or any highlighted field. The workflow may require a resolution, approval, completed subtask, or permission you do not have.
For example, a transition can require a release version before an issue moves to Done. Add the required value if you know it, or ask the project owner which value applies.
You might be wondering: what if the expected transition is missing? Your role may not have permission, or the project’s workflow may use a different path. Check with a Jira administrator before trying to work around the restriction.
If the ticket closes and later needs more work, follow your team’s reopening process. Some workflows offer a Reopen transition; others require a new linked issue to preserve the original history.
ONES.com Solution for Project and Knowledge Management
ONES.com combines project management and knowledge management in one platform. ONES Project is a Jira alternative for teams that need issue tracking and customizable workflows, while ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

For a team evaluating how to manage tickets and project work, the practical question is whether the platform supports its existing workflow without adding unnecessary complexity. ONES.com offers Jira-compatible workflows, reporting, custom fields, sprint management, and automation.
Core capabilities
- Workflow setup takes too much administration: ONES Project supports custom workflows, so teams can shape status transitions around their process. The result is a clearer route from active work to closure.
- Teams need familiar issue handling: Jira-compatible workflows help teams carry over established ticket practices. That can make a platform change easier to evaluate for Jira-oriented teams.
- Reports require too much manual effort: Built-in reporting gives teams a way to review project progress without assembling every view separately.
- Default fields do not capture enough detail: Custom fields let teams record information relevant to their work, such as a closure reason or service area.
- Sprint work is hard to coordinate: Sprint management supports planning and tracking work across an iteration, giving teams a clearer view of what remains open.
- Repeated actions slow the team down: Automation can handle suitable routine workflow actions, reducing the need for people to repeat the same updates manually.
- Extra plugins add maintenance: Native project capabilities can reduce reliance on plugins for supported needs, giving administrators fewer add-ons to manage.
- Deployment requirements limit platform choices: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its cloud and self-hosted versions have full feature parity.
ONES.com offers a free plan for up to 30 seats. Teams can assess how its workflows fit their needs before deciding whether a deployment option and separate products suit their environment.
Application scenarios
Software team moving from Jira: A development group can map its issue statuses and sprint routines into ONES Project, then configure fields for release checks and closure notes. Jira-compatible workflows give the team familiar patterns to evaluate.
Organization with restricted network requirements: A team that cannot use a public cloud service can consider On-Premise, Private Cloud, or Air-gapped deployment options. Full feature parity across cloud and self-hosted versions helps maintain access to supported capabilities.
Team connecting project work with internal knowledge: A group can use ONES Project for tickets and ONES Wiki for knowledge management when both fit its needs. Because the products are sold separately, a team can choose the one that addresses its immediate requirement.
Common Challenges When Closing Jira Tickets
- The ticket is closed without a clear outcome. Add a short note explaining what changed or why the request ended. A statement such as “completed” may not help the next person understand what happened.
- The status looks final, but the issue remains unresolved. Check the resolution field and your project’s workflow rules. Ask an administrator whether the transition should set a resolution automatically.
- A required field blocks the transition. Read Jira’s validation message and complete the field with accurate information. If you are unsure what to enter, ask the project owner rather than guessing.
- The ticket is reopened after closure. Review whether the original acceptance criteria were met and whether the closing note described the verification. If new work has emerged, follow the team’s reopening or linked-issue practice.
- Different team members close similar issues differently. Agree on a small set of status and resolution meanings, then share a concrete example for common outcomes such as fixed, duplicate, or declined.
Frequently Asked Questions
What is the difference between resolving and closing a Jira ticket?
It depends on your project’s workflow. Some teams use Resolved when work is complete and reserve Closed for a later confirmation. Other teams treat the terms as equivalent or use a status such as Done.
Check your project’s workflow and resolution rules before choosing a transition. The important point is that the status and resolution should describe the outcome consistently.
Why can’t I see a Close button in Jira?
Your project may use a different transition name, such as Done or Resolve. The workflow may also limit transitions based on the ticket’s current status, your permissions, or required fields.
Check the available issue actions and any validation message. If the expected transition is still missing, ask a Jira administrator or project lead to confirm the correct workflow path.
Can I close a Jira ticket without setting a resolution?
Some workflows allow this, while others require a resolution before the transition completes. Even when Jira does not require one, your team may rely on resolution values for searches and reports.
Use the resolution field when your workflow provides it, and select the value that matches the result. If the field is absent, check whether your project sets it automatically.
Should I close a ticket when its fix has not been released?
Follow the status rules your team uses for development, testing, and release. A team may consider implementation complete before deployment, or keep the issue open until the change reaches the intended environment.
Make the ticket’s status and closing note clear about what has happened. If release tracking is separate, link the relevant release work or create a follow-up issue.
What should I write in a Jira closing comment?
Summarize the outcome and mention how it was checked. For example: “Updated the account permissions and verified access with a test account.” For a duplicate or declined request, explain that outcome and link related work when useful.
A concise, specific note is easier to understand than a generic “done.” Keep unresolved follow-up work visible through a separate issue or a clear explanation.
Conclusion
Closing a Jira ticket well means more than changing its status. Confirm the work, add a clear outcome, use the correct transition, and verify that the resolution matches what happened.
When workflow rules or permissions get in the way, check the validation message and ask the project owner rather than guessing. A consistent closure process helps your team avoid confusion and makes completed work easier to understand later.