How to Close a Ticket in Jira: A Quick Step-by-Step Guide

Not sure how to close a ticket in Jira? Follow this quick guide to complete the right workflow steps and verify it’s closed. Read now!

To close a ticket in Jira, open the issue, select the available Close transition, complete any required fields, and confirm the change. The ticket closes only when your project’s workflow allows that transition.

It can be confusing when a ticket looks finished but still appears open, or when the Close option is missing. Choosing the wrong status can also make reports and queues less accurate.

But here's the truth: closing a Jira ticket is usually quick once you know where to find the transition and what your workflow requires. Here’s how to do it, check that it worked, and handle common roadblocks.

How to Close a Ticket in Jira

Open the issue. Find the ticket through Jira search, a project board, or your assigned work list. Select its issue key or summary to open the full issue view.
Check the current status. Look near the issue summary for its status, such as Open, In Progress, or Resolved. Some workflows allow closing only from certain statuses.
Find the Close transition. Select the status button or transition menu near the top of the issue. Depending on your Jira layout and workflow, the option may appear as Close, Done, or another transition name.
Complete any required fields. Jira may ask for a resolution, a closing comment, or another required detail. Add a concise note, such as “Verified the fix in version 4.2,” when it helps the next person.
Confirm the transition. Select the final confirmation button if Jira displays one. Check the issue status afterward to ensure the workflow moved it to the intended closed state.

For example, if a bug has been fixed and tested, you might add a closing comment and select Close. If Jira offers only Resolve, use the available transition and follow your team’s process.

Jira product screenshot

Closing, Resolving, and Completing a Ticket

These statuses can mean different things

Jira statuses describe the current step in a workflow. A team might use Open, In Progress, Resolved, and Closed, while another team may use a shorter sequence.

In many workflows, resolving means the work has a proposed outcome, such as a fix or a decision. Closing can signal that the outcome has been confirmed and no further action is expected.

Check the resolution as well as the status

The status and resolution are separate issue fields. A ticket may show a finished status while its resolution remains empty, or it may retain a resolution after someone reopens it.

Here’s why: reports and filters may use the resolution field to distinguish completed issues from active ones. If your team tracks resolution, confirm that Jira sets an appropriate value during the transition.

What to Do When the Close Option Is Missing

Check your current status and workflow

A workflow may allow closing only after a ticket reaches a particular status. For example, a team might require a ticket to move from In Progress to Resolved before it can be closed.

Review the available transitions first. If Jira shows a route to Resolved or Done, follow that route and check whether a closing transition appears afterward.

Check your project access

Your Jira permissions may limit which transitions you can perform. If a colleague can close the same issue and you cannot, ask a project administrator to check your access and the workflow conditions.

Don’t try to change the issue’s status by editing unrelated fields. That can leave the ticket inconsistent with your team’s process.

Look for required information

Some transitions require a resolution, a comment, or another field before Jira will continue. A prompt or validation message usually identifies what’s missing.

For instance, a support workflow might require a resolution category. Choose the correct category, then try the transition again.

How to Confirm the Ticket Is Really Closed

Check the status after the transition

After closing the issue, look at its status near the summary. Confirm that it matches the destination your team considers closed, such as Closed or Done.

If Jira returns an error or the status stays unchanged, the transition may not have completed. Read any message on the issue and address the missing field or permission restriction.

Review resolution and activity

When your workflow tracks resolution, confirm that the issue has the expected value. You can also review the activity history to see the transition and any closing comment.

The best part? A short verification takes only a moment and can prevent finished work from staying in active queues. A clear comment also tells teammates why the issue was closed.

When to Close, Reopen, or Leave a Ticket Resolved

Close it when the outcome is confirmed

Close a ticket when the requested work is complete and your team’s checks are satisfied. A developer might close a bug after testing the fix; a service team might close a request after confirming the customer received help.

Reopen it when more work is needed

If the reported problem returns or the fix fails verification, use the available reopen transition. Add a note explaining what happened, such as “The issue still occurs on mobile after the update.”

Keep it resolved when follow-up remains

Some teams use a resolved state for work awaiting confirmation. If your team expects a customer or reviewer to verify the result, leave the ticket in that state until the check is complete.

You might be wondering: which status should you choose if the labels differ? Follow the workflow’s meaning and your team’s conventions rather than relying on the label alone.

Managing Ticket Workflows Beyond Jira: ONES.com

ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. Its project management product, ONES Project, is a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. The products are sold separately.

ONES.com product screenshot

Value proposition

If you need structured issue transitions, reporting, or self-hosted deployment options, ONES Project offers project workflows without requiring every team to use the same setup. Its cloud and self-hosted versions have full feature parity.

Core capabilities

Pain: Your Jira workflows don’t match how teams complete work. ONES capability: Create custom workflows. Result: Teams can define transitions that reflect their ticket lifecycle.
Pain: Issue forms lack the details your team needs. ONES capability: Configure custom fields. Result: Tickets can capture relevant information at the right stage.
Pain: Sprint planning and issue tracking feel disconnected. ONES capability: Use sprint management. Result: Teams can organize planned work alongside tickets.
Pain: Repetitive updates take time. ONES capability: Set up automation. Result: Routine workflow actions can happen automatically.
Pain: Progress is difficult to review. ONES capability: Use built-in reporting. Result: Teams can inspect project status and delivery trends.
Pain: Your team already relies on Jira-style processes. ONES capability: Configure Jira-compatible workflows. Result: You can carry familiar workflow patterns into a different project platform.
Pain: Plugin dependence adds maintenance work. ONES capability: Use native project features for workflows, reporting, fields, sprints, and automation. Result: Teams may be able to reduce plugin requirements.
Pain: Cloud hosting doesn’t meet deployment needs. ONES capability: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. Result: You can select an environment that fits operational requirements.

Application scenarios

A software team could create a workflow that moves bugs through triage, development, testing, and closure. Custom fields could capture severity and affected versions, while automation handles routine assignments.

An organization with restricted network requirements could evaluate an Air-gapped or On-Premise deployment. ONES.com offers a free plan for up to 30 seats, which can help a small team evaluate its project workflows.

Common Challenges When Closing Jira Tickets

The ticket still appears open. Check whether the transition completed and whether the destination status matches your team’s definition of closed. Review any error message before trying again.
The Close transition is unavailable. Check the current status, workflow conditions, and your project permissions. Ask a Jira administrator to review the workflow if the expected transition remains missing.
The issue has no resolution value. Confirm whether your workflow requires a resolution field. Select the appropriate value through the transition prompt rather than changing unrelated fields.
Reports still include the ticket as active. Verify both its status and resolution. Ask your project administrator which fields the relevant board or report uses to identify completed work.
The ticket was closed too soon. Use the workflow’s reopen transition, then explain in a comment what still needs attention. This keeps the next action clear for the assignee.

FAQs About Closing Jira Tickets

Can I close a Jira ticket without a resolution?

That depends on your project’s workflow. Some workflows set a resolution automatically when you close an issue, while others require you to select one. If the ticket closes but reports still treat it as unresolved, ask your Jira administrator whether the workflow should populate the resolution field during the transition.

Why can I resolve a ticket but not close it?

Your workflow may separate resolution from closure. It could require a review, customer confirmation, or another status change before closing becomes available. Check the issue’s current status and available transitions. If the workflow appears to block an expected action, ask a project administrator to confirm its conditions and your permissions.

Can I reopen a closed Jira ticket?

Many Jira workflows provide a reopen transition, but the exact option depends on project configuration and your permissions. Open the issue and check its available status transitions. If reopening is allowed, add a short comment explaining why more work is needed. If no reopen option appears, contact your Jira administrator for help.

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

Not necessarily. Jira status names and workflow meanings vary by project. One team may use Done as its final status, while another uses Closed after a separate review. Check the workflow and your team’s conventions, then confirm how reports identify completed issues.

Conclusion

To close a Jira ticket, open the issue, use the transition your workflow provides, complete required details, and verify the resulting status. Check resolution too if your team relies on it for reporting.

If the Close option is missing, investigate the issue’s current status, workflow rules, required fields, and your permissions. A clear closing comment helps teammates understand what happened.

But here's the truth: a ticket is only truly finished when its status matches the work completed and your team’s process. Follow the transition carefully, confirm the result, and your Jira queue will be easier to trust.