How to Close a Jira Ticket: A Step-by-Step Guide [2026]

Not sure how to close Jira ticket? Follow this 2026 guide to finish issues correctly and avoid workflow errors. Click to discover.

You close a Jira ticket by moving it through the workflow until it reaches the project’s final status, such as Done or Closed. Usually, you open the ticket, complete the required work, add a useful resolution, and select the correct transition.

Still, a ticket can refuse to close because a required field is empty, an approval is missing, or your Jira workflow uses a different status name. Closing the wrong way can also hide unfinished work and distort sprint reports.

But here's the truth: closing a Jira issue is easy when you follow the workflow instead of guessing. This guide shows each step, explains common blockers, and helps you choose the right final status with confidence.

How to Close a Jira Ticket

Follow these steps to close a Jira ticket correctly. The button names may differ slightly because each Jira project can use a customized workflow.

Open the Jira issue. Find the ticket through your project board, backlog, search results, or issue link. Check that you are working on the correct issue key and summary.
Review the work. Confirm that the requested task is complete. Check acceptance criteria, linked issues, comments, testing notes, and any required approvals.
Update the issue details. Add a clear comment, adjust the assignee if needed, and complete fields such as environment, fix version, or resolution.
Choose the workflow transition. Select Close, Resolve, Done, or another final transition near the top of the issue. Jira may place this action inside a status menu.
Complete required fields. If Jira opens a transition screen, provide the requested information. A resolution such as Fixed, Won’t Fix, or Duplicate may be mandatory.
Confirm the new status. Check the status badge after saving. The issue should show the final workflow state, and the resolution should match the actual outcome.
Verify related work. Review linked issues, subtasks, deployments, and notifications. A parent ticket may remain open if a subtask or approval still needs attention.

Here's why the final check matters: Jira treats status and resolution as separate pieces of information. An issue can appear complete while still carrying an incorrect or empty resolution.

Jira product screenshot

What “closed” means in Jira

Jira uses workflows to control how an issue moves from one state to another. A project might use To Do → In Progress → In Review → Done, while another uses Open → In Development → Resolved → Closed.

In many projects, Done means the team finished the work, while Closed means the issue passed a final administrative check. Your project’s workflow determines the exact meaning.

How to close a ticket from the issue view

Open the issue and look for a transition button near its current status. Select the final action, complete any required fields, and save the transition.

If you see an overflow menu with three dots, open it and look for a status transition. Some Jira layouts place actions under Workflow, Status, or a similar menu.

How to close a ticket from a board

On a Kanban or Scrum board, drag the issue card into the final column if your project allows board transitions. You may also open the card and choose the final status manually.

Dragging the card may trigger a form. Complete every required field before leaving the board. If the move fails, open the issue directly because Jira usually shows more detailed guidance there.

Prepare the Issue Before Closing It

A clean closure begins before you click the final transition. Take two minutes to confirm that the ticket tells the complete story for someone who may review it later.

Check the acceptance criteria: Each requested outcome should be complete or clearly marked as excluded.
Review the assignee: The person responsible for the final action should be correct.
Confirm linked work: Related bugs, subtasks, approvals, or follow-up actions should have an appropriate status.
Add a closing comment: Explain what changed, how it was checked, and whether anything remains.
Verify the resolution: Use Fixed for completed work, Duplicate for repeated issues, or another value that reflects the outcome.
Check the fix version: Add the relevant release when the project tracks delivery by version.

For example, imagine a ticket that says, “Add password reset emails.” Before closing it, you might confirm that the email works, the expiration link behaves correctly, and the change passed review.

You might leave this comment: “Password reset emails now include a 30-minute link expiration. Tested successful resets, expired links, and unknown email addresses in staging.”

What to Do When Jira Will Not Let You Close the Ticket

Jira usually blocks a transition for a specific reason. The cause may be a missing field, a permission rule, an unfinished approval, or a workflow condition.

Check for required fields

A transition screen may require a resolution, fix version, comment, or custom field. Look for red validation messages and complete every highlighted field.

If the form disappears before you can read the message, reopen the issue and try the transition again. An administrator may need to adjust the transition screen if the required field is unclear.

Check your permissions

You may be able to edit the issue without having permission to transition it. Ask a Jira administrator or project lead to check your Transition Issues permission.

For example, a support agent might update comments but only a developer or team lead may move an issue into Closed.

Check workflow conditions

Some workflows allow closure only after testing, review, or approval. The issue may need to move through In Review before the final transition appears.

Look for pending approvals, unresolved subtasks, or a missing reviewer. Completing that step often makes the closing action available.

Check whether the issue is already resolved

An issue with a Resolved status may not need a second resolution. Jira may require a separate Close transition, or the project may treat Resolved as its final state.

Ask your project lead which status counts as complete for reporting. This avoids moving an issue backward simply to make the status label look familiar.

Choosing the Right Resolution

Status describes where the issue sits in the workflow. Resolution describes why the issue is finished. Choosing the right resolution keeps reports and future searches accurate.

Resolution	When to use it
Fixed	The team completed and verified the requested change.
Duplicate	Another issue already tracks the same problem.
Won’t Fix	The team reviewed the issue and decided not to make the change.
Cannot Reproduce	The team could not reproduce the reported behavior after reasonable checks.
Incomplete	The request lacks enough information or cannot proceed as described.

Use the resolution that explains the outcome rather than selecting the first available option. A duplicate bug should not receive Fixed simply because the original bug was corrected elsewhere.

The best part? A useful resolution makes future reporting easier. When a manager reviews closed issues, the resolution quickly explains whether the team delivered, declined, merged, or could not verify the request.

Closing Different Jira Issue Types

The right closing behavior depends on the issue type. A bug, story, task, and subtask may share similar statuses while requiring different checks.

Closing a bug

Confirm that the defect is fixed in the intended environment. Add reproduction details, test results, and the release or build where the fix is available.

If the behavior still occurs, leave the bug open or move it to a status such as Needs More Work. Closing it early can make defect reports look healthier than they are.

Closing a story

Check every acceptance criterion and confirm that the product owner or assigned reviewer has accepted the result. A story may also require completed subtasks before it reaches Done.

Closing a task

Explain the completed action and attach relevant test results or review notes when appropriate. Administrative tasks often need a short completion comment because their outcome is not visible in the product.

Closing a subtask

Close the subtask after its own work is complete. Then review the parent issue because closing every subtask may not automatically close the parent.

Closing a service request

Confirm that the requester received the response or outcome. Some service workflows require a customer notification or approval before the request can move to its final status.

How to Reopen a Closed Jira Ticket

Reopen a Jira ticket when new information shows that the work is incomplete, the defect returned, or the original resolution was incorrect.

Open the closed or resolved issue.
Choose Reopen, Reopen Issue, or the equivalent workflow transition.
Explain why the issue needs more work.
Clear or update the resolution if Jira asks you to do so.
Assign the issue to the person responsible for the next action.
Move it into the appropriate active status, such as Open or In Progress.

For example, a payment bug marked Fixed may return after a new release. Reopening the original issue preserves the history and connects the regression to the earlier work.

Let me explain: reopening is usually better than creating a disconnected duplicate when the new problem clearly relates to the original ticket. Create a new issue when the scope, cause, or delivery plan is substantially different.

Natural Jira Alternative: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com combines project management and knowledge management in one platform. ONES Project is a Jira alternative for teams that need structured workflows, reporting, and flexible deployment choices.

It can suit teams that want Jira-compatible workflows with fewer connected plugins and an on-premise option. ONES Project and ONES Wiki are sold separately, so you can choose the product that matches your operating needs.

Core Capabilities

Complex ticket closure is difficult → Custom workflows and fields → Build status paths that reflect review, testing, approval, and final closure.
Teams lose visibility across active work → Built-in reporting → Track completed issues, unresolved work, cycle time, and workflow progress in one place.
Manual status changes create delays → Automation → Trigger routine actions when issues change status, receive approval, or meet defined conditions.
Sprint work becomes hard to monitor → Sprint management → Plan iterations, organize work, and compare committed items with completed items.
Teams depend on many add-ons → Native project features → Reduce plugin reliance by using integrated workflows, fields, reporting, and automation.
Existing Jira habits slow migration → Jira-compatible workflows → Preserve familiar issue and workflow patterns while adapting the platform to team requirements.
Security requirements restrict cloud-only tools → On-premise, private cloud, and air-gapped deployments → Choose an environment that fits operational and network controls.
Different hosting models create feature gaps → Full feature parity between cloud and self-hosted versions → Select deployment based on infrastructure needs rather than losing core capabilities.

Application Scenarios

Software team with approval gates: A development team can create separate transitions for code review, quality checks, release approval, and closure. A ticket cannot reach its final status until the required steps are complete.

Restricted-network engineering group: A team with air-gapped infrastructure can use a self-hosted deployment while maintaining structured issue tracking and reporting within its controlled environment.

Growing product organization: Product, engineering, and support teams can use project workflows alongside a separate knowledge platform, helping each group manage its own responsibilities without forcing every process into the same workspace.

Common Challenges When Closing Jira Tickets

The final status is missing

Problem: You can edit the issue, but no close or resolve action appears.

Solution: Check your transition permission and the current workflow state. The issue may need to pass through review or approval first.

The resolution is incorrect

Problem: The issue shows a resolution that does not match the outcome.

Solution: Reopen or edit the issue according to your project rules, then choose the resolution that accurately describes what happened.

Closing the parent does not close subtasks

Problem: The parent issue appears complete while subtasks remain active.

Solution: Review each subtask separately. Close completed subtasks and create follow-up work for anything unfinished.

A closed issue reappears in active reports

Problem: Reports still count the ticket as unresolved.

Solution: Check whether the final status belongs to the project’s completed status category. Also confirm that the resolution field is populated correctly.

The team closes tickets too early

Problem: Issues reach the final column before testing, customer confirmation, or release work finishes.

Solution: Add explicit workflow gates and define what “done” means for each issue type. A short checklist can prevent premature closure.

FAQs About Closing Jira Tickets

Can I close a Jira ticket without a resolution?

That depends on your workflow. Some Jira projects require a resolution before an issue can reach its final status, while others allow closure without one. If the transition fails, check the required fields on the transition screen. If no resolution is required, adding a clear closing comment still helps explain the outcome.

Is “Done” the same as “Closed” in Jira?

No. Both can represent completed work, but their meaning depends on the project workflow. Some teams use Done as the final status, while others move issues from Resolved to Closed after a final review. Check the status category and team definition before changing an issue.

Why can’t I close a Jira issue?

Common reasons include missing permissions, required fields, pending approvals, unresolved subtasks, or a workflow condition. Open the issue directly and try the transition again so Jira can show the validation message. If the problem continues, ask a project administrator to inspect the workflow and your project permissions.

Should I close a duplicate Jira ticket?

Yes, when another issue already tracks the same request or defect. Link the duplicate to the original issue, add a short explanation, and use the Duplicate resolution if your workflow provides it. Avoid using Fixed, because that suggests the duplicate issue received its own implementation.

Can I reopen a closed Jira ticket?

Usually, yes, if your workflow includes a reopen transition and you have permission to use it. Explain what changed, update the resolution when required, and assign the issue for follow-up work. If no reopen action exists, a Jira administrator may need to add one or move the issue manually.

Conclusion

To close a Jira ticket properly, verify the work, complete required fields, choose the correct final transition, and confirm the resolution. Then review related subtasks, approvals, and reports.

But here's the truth: a closed status is useful only when it reflects real completion. A clear workflow, accurate resolution, and concise closing comment protect your reports and help teammates understand what happened.

When Jira workflows become difficult to manage, ONES Project offers a Jira alternative with custom workflows, automation, reporting, sprint management, and flexible deployment options. Choose the workflow that makes completion visible, consistent, and easy to trust.