How to Change a Jira Ticket Type: 7 Steps, Checks, and Tips
Need to change jira ticket type without losing details? Use these 7 steps to check fields, permissions, and workflows—and avoid common issues. Read now.
Changing a Jira ticket type can be simple, until the new type requires different fields, permissions, or workflow statuses. Choosing the wrong option may leave the ticket in a confusing state or interrupt work already underway. The good news: you can usually change an issue’s type with Jira’s Move action, then review any fields and status mappings Jira requests. A few checks before and after the change help prevent missing information and unexpected workflow changes. Here’s a practical seven-step guide, plus advice for handling common roadblocks. Whether you’re turning a task into a bug or correcting an issue created under the wrong type, you can make the change with care and verify the result.
How to Change a Jira Ticket Type in 7 Steps
In Jira, a “ticket type” is usually called an issue type. The usual route is to open the issue, choose More and Move, then select the new issue type and complete Jira’s prompts.
Jira’s labels can vary by product version and project configuration. If you don’t see the same options below, your permissions or project settings may differ.
Open the ticket. Go to the issue you want to update and check its key, summary, current type, and project. Confirm you’re working on the right ticket before making changes.
Open the Move action. Select More near the issue controls, then choose Move. If the option is missing, check your project permissions or ask a Jira administrator whether you can move issues.
Keep the ticket in its current project. If Jira asks you to select a destination project, choose the existing project unless you intend to move the ticket elsewhere too. Changing a type and changing a project are separate decisions.
Choose the new issue type. Select the intended type, such as Bug, Task, or Story. Check the name carefully: similar types can follow different workflows or require different fields.
Review status mapping. If Jira asks you to map the current status to a status in the new workflow, choose the closest valid match. For example, map an active ticket to an equivalent in-progress status rather than sending it back to the start.
Complete required fields. Jira may request fields that the new type requires. Fill in relevant details, and review any field values Jira asks you to confirm or change before continuing.
Confirm and verify. Submit the change, then reopen the ticket. Check its type, status, key fields, comments, and activity history. If the result looks wrong, pause and contact your Jira administrator before making more changes.
But here’s the truth: changing the label is only one part of the operation. Jira may also need to reconcile the issue with the destination type’s fields and workflow.

Before You Change the Issue Type
First, be clear about the outcome you need. Turning a Task into a Bug may be appropriate when the work is a defect; moving a ticket to another project is a different operation. A quick check with the assignee can prevent an unnecessary change.
Then check whether the new type is available in the project. Jira projects can use different issue types, and administrators may control which types appear. For example, a project configured for Stories and Bugs might not offer an Epic as a selectable option.
Here’s why: issue types can affect available fields, workflow paths, and reporting. A ticket moving from Task to Bug may need a priority or environment detail that its original type did not require.
What Jira May Change During the Move
The Move action can prompt you to map statuses when the destination type uses a different workflow. Imagine a ticket currently marked “In Review” moving to a type with “Ready for QA” and “Done” stages. Jira may ask you to choose the closest matching status.
Field prompts also deserve attention. A required field for the new type may be empty, or a field used by the old type may not apply. Enter accurate information where needed; don’t guess just to get past a prompt.
Jira may show a review screen before you confirm. Read it as a checkpoint, not a formality. If the project, issue type, or status mapping is wrong, go back before submitting.
Checks to Run After Changing a Ticket Type
Start by confirming the issue shows the intended type and remains in the expected project. Then check that its status still reflects the actual work. A ticket can look correct at a glance while sitting in an unsuitable workflow stage.
Review the fields that matter to your team, including priority, assignee, due date, and any type-specific details. For a Bug, for example, confirm that the steps to reproduce and affected environment are still clear.
Finally, look at the issue’s activity history and notify the assignee if the change affects their next step. A short message such as “Changed this from Task to Bug; please add reproduction steps” gives the update context.
When Jira Doesn’t Offer the Type You Need
If the new type is absent from the menu, the project may not include it in its issue type configuration. Ask a Jira administrator to confirm the project’s available types and whether the type can be added.
If you can’t see Move, you may lack the required permission. Access can vary by project and Jira configuration, so ask an administrator to review your permissions rather than trying to work around them.
When Jira rejects the move because of a required field or workflow mismatch, read the prompt and correct the specific issue. If you’re unsure how to map a status, ask the project owner before proceeding. That is safer than choosing a value that misrepresents the ticket’s progress.
A Broader Issue-Management Option: ONES.com
ONES.com brings project management and knowledge management together in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so teams can choose the capabilities they need.

For teams reviewing Jira workflows, ONES Project is a Jira alternative with issue management, sprint planning, and workflow configuration. Its familiar workflow options can help teams structure work while reducing reliance on extra plugins. ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with full feature parity between cloud and self-hosted versions.
Core Capabilities
Work types don’t fit the team’s process: Configure custom workflows and fields in ONES Project, so teams can represent their work with a process that matches their needs.
Sprint work is hard to coordinate: Use sprint management to plan and track work, helping the team see what is in progress and what remains.
Repeated actions take time: Set up automation for recurring workflow tasks, reducing manual steps for common transitions.
Progress is difficult to review: Use built-in reporting to make project progress easier to inspect without relying on multiple add-ons.
Teams need familiar issue workflows: Jira-compatible workflows help teams adapt existing ways of organizing and moving work.
Field requirements vary by work type: Create custom fields and workflows to capture information that matters for different kinds of work.
Deployment requirements differ: Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment to suit operational needs.
Project knowledge is scattered: Use ONES Wiki as a separate knowledge-management product alongside ONES Project when teams want a dedicated place for shared guidance.
Application Scenarios
A team moving from Jira: A project group that relies on custom workflows, sprint planning, and reporting can assess ONES Project as a Jira alternative. It can compare its existing process with the platform’s workflow and field options before deciding what to migrate.
A restricted-network organization: An organization with deployment constraints can evaluate an On-Premise, Private Cloud, or Air-gapped deployment. This gives the team a way to consider project management under its own environment requirements.
Common Challenges and Practical Fixes
The Move option is missing. You may not have permission to move the issue. Ask a Jira administrator to check your access, or have an authorized teammate perform the change.
The intended type isn’t available. The project may not be configured to use that issue type. Ask the project administrator to review the available types before changing project configuration.
Jira requests unfamiliar fields. The new type may require information the original type didn’t collect. Check with the ticket’s assignee or project owner, then enter relevant details.
The status mapping seems unclear. Workflows may use different status names or stages. Ask the project owner which destination status reflects the ticket’s actual progress.
The change causes confusion for teammates. A type change can affect how people triage or report work. Add a comment explaining the reason and alert anyone whose next action depends on it.
Frequently Asked Questions
Can I change a Jira ticket type without changing its project?
Usually, yes. Use the Move action and keep the current project selected when Jira asks where the issue should go. Then select the new issue type. Jira may still ask you to map a status or fill required fields. Review those prompts carefully, because the new type may use different settings even though the project stays the same.
Why can’t I see the Move option in Jira?
The option may be hidden because of your Jira version, project configuration, or permissions. Check the issue’s More menu first. If Move is unavailable, ask a project or Jira administrator to confirm whether you have permission to move issues and whether the project supports the requested type.
Will changing the issue type delete comments or work history?
The Move action is designed to change an issue’s project or type while retaining the issue’s history, but what you see can depend on the Jira setup. After the change, check the activity history, comments, and important fields. If the ticket is sensitive or business-critical, ask your Jira administrator about the project’s configuration before proceeding.
Can I change an issue type back if I choose the wrong one?
You can often run the Move action again and select the original type, provided it is available and you have the required permissions. Jira may ask you to map statuses or supply fields again. Before reversing the change, check whether the workflow has advanced or whether teammates have acted on the ticket.
Conclusion
To change a Jira ticket type, open the issue, use More and Move, select the intended type, and review Jira’s prompts before confirming. Then verify the issue’s type, status, fields, and history.
A missing type, unavailable Move action, or unclear status mapping usually calls for an administrator or project owner. Taking a moment to check the result helps avoid a ticket that looks right but no longer matches the team’s workflow.
Changing an issue type is manageable when you know what Jira may ask and what to inspect afterward. Use the seven steps as a careful checklist, and explain the change to anyone relying on the ticket.