How to Change a Jira Ticket Type: Step-by-Step Guide (2026)
Need to change a Jira ticket type? Follow this Jira change ticket type guide to use the Move workflow without recreating an issue. Read now.
A Jira ticket can start as a task and later turn out to be a bug, story, or another issue type. If the type no longer fits, changing it can make boards, reports, and workflows harder to trust.
The confusing part is that Jira may hide the change behind a move action, and the available choices depend on your project setup and permissions. A rushed change can also prompt you to map fields or statuses you did not expect.
But here's the truth: you can usually change a ticket’s type without recreating the issue. This guide walks you through Jira’s Move workflow, explains what to check before confirming, and helps you troubleshoot common roadblocks. You’ll also learn when a different project management setup may make issue changes easier to manage.
How to Change a Jira Ticket Type
In most Jira projects, open the issue, select More, choose Move, and pick the new issue type. Review any field or status mapping Jira requests, then confirm the change.
Open the ticket. Navigate to the Jira issue you want to change. Check its project, current issue type, status, and key fields before moving forward.
Open the Move action. Select More on the issue and choose Move. The location or wording can vary with your Jira interface and project configuration.
Keep the same project, if that is your goal. If Jira asks you to select a destination project, choose the current project. Then select the new issue type, such as Bug, Story, or Task.
Review field and status prompts. Jira may ask you to map statuses or provide required fields for the new type. Check each choice carefully; a Bug may require details that a Task did not.
Confirm the change. Review the summary of the move and submit it. Reopen the issue afterward to verify its type, status, and important fields.
For example, if a Task is actually a customer-facing defect, changing it to Bug can place it into a bug workflow. Before you confirm, check whether required fields such as severity or environment need values.
What to Check Before Changing an Issue Type
Changing an issue type can affect the fields and workflow options Jira presents. Take a moment to review the ticket’s current details and the requirements attached to its new type.
Look for required fields, status compatibility, and any project-specific rules. If a ticket is in a status that the new type cannot use, Jira may ask you to select a different status during the move.
Here's why: an issue type often determines which fields and workflow apply. For instance, a Story might use story points, while a Bug might request severity and reproduction steps.
If the ticket is important or linked to active work, tell its assignee before changing it. That simple heads-up helps avoid confusion when the issue appears differently in a board or report.
How Jira Handles Different Project Setups
Jira’s exact screens depend on the project type, configuration, and your permissions. Company-managed and team-managed projects can offer different issue type options and workflow controls.
In a company-managed project, administrators typically control issue types, fields, and workflows through shared configuration. A ticket may need an administrator’s help if its destination type is missing or its workflow cannot accept the current status.
Team-managed projects often keep more configuration within the project itself. Even so, the available actions can vary, so follow the choices shown in your Jira interface rather than assuming every project has identical settings.
You might be wondering: what if you cannot see Move? Your account may lack permission, or the project may restrict the action. Ask a project administrator to check your access and the project’s issue type setup.
What Changes—and What Usually Stays the Same
A type change updates how Jira classifies the issue. It can affect the available fields, workflow, board grouping, and reporting categories, especially when the new type has different configuration.
The issue generally retains its identity, such as its issue key, and its existing activity remains attached. However, field values may need adjustment, and a status may require mapping to a valid option for the new workflow.
For example, changing a Story to a Bug may leave the issue’s description and comments available, while prompting you to add bug-specific details. Check the result rather than assuming every field transferred exactly as expected.
After the change, review linked issues, board placement, filters, and reports that depend on issue type. If a sprint board stops displaying the ticket, check its filter and the board’s issue type settings.
Changing Types for Several Jira Issues
If many tickets need reclassification, Jira’s bulk change feature may save time. Select the relevant issues in an issue search or project view, then look for a bulk operation that supports moving issues.
Bulk actions require suitable permissions and may not offer the same options in every project. Test the process with a small, representative group first, especially when the tickets have different statuses or custom fields.
Let me explain: changing ten similar Tasks to Bugs is easier to validate than changing dozens of mixed issue types at once. Check a few results before applying the same change across a larger group.
Keep a clear list of the affected issue keys and intended new types during a bulk operation. That makes it easier to spot an incorrect classification and review the outcome with your team.
ONES.com brings project management and knowledge management together in one platform, with ONES Project available as a Jira alternative. Teams can use built-in workflows and reporting while reducing reliance on plugins for common project needs.
ONES Project supports Jira-compatible workflows, custom fields, sprint management, and automation. It is sold separately from ONES Wiki, the knowledge base product, so teams can choose the capabilities that fit their needs.
Core Capabilities
Issue classification feels disconnected → Jira-compatible workflows → Map project processes into familiar workflow patterns and manage issue types within a consistent project setup.
Teams rely on add-ons for everyday reporting → Built-in reporting → Review project progress using reporting capabilities included with ONES Project.
Default fields do not capture team needs → Custom fields → Track details such as severity, release, or customer impact in fields suited to the team’s process.
Issue transitions do not match the real work → Custom workflows → Configure workflow steps around how tickets move from intake to completion.
Sprint planning is scattered across processes → Sprint management → Organize work into sprints and follow delivery progress within the project environment.
Repeated project steps take manual effort → Automation → Set up routine actions that help reduce repetitive work across issue handling.
Plugin dependence complicates maintenance → Native feature parity → Use core project capabilities built into the platform, which can reduce the number of plugins needed for common workflows.
Deployment requirements limit cloud use → Multiple deployment options → Choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment, with feature parity between cloud and self-hosted versions.
Application Scenarios
Product teams refining ticket intake: A team that often changes Tasks into Bugs can define issue types, required fields, and workflow steps that reflect how defects are reviewed and resolved.
Organizations with restricted environments: Teams that cannot use a public cloud deployment can evaluate On-Premise, Private Cloud, or Air-gapped options while retaining access to the platform’s project capabilities.
Teams reducing plugin overhead: A project group that depends on several add-ons for reporting and workflow automation can assess whether built-in reporting and automation cover its common requirements.
Common Challenges When Changing Jira Ticket Types
Move is missing: Your account may not have the required permission, or the project may restrict moving issues. Ask a Jira administrator to review access and available actions.
The desired type is unavailable: The issue type may not be configured for the project. Ask an administrator whether it can be added or whether another type better matches the work.
Jira requests field updates: The new issue type may have required fields that the current ticket lacks. Complete the prompts with accurate details before confirming.
The current status cannot carry over: The destination workflow may not include that status. Choose a suitable mapped status and check with the project owner if the right option is unclear.
The ticket disappears from a board: The board’s filter or configuration may exclude the new issue type. Review the board settings and confirm that its filter includes the updated type.
FAQs About Changing Jira Issue Types
Can I change a Jira issue type without changing its project?
In many Jira setups, yes. Open the issue, choose More and then Move, keep the current project as the destination, and select the new issue type. Jira may still ask you to map a status or fill in required fields. If the project does not offer the intended type, ask an administrator to review its configuration.
Will changing a Jira ticket type change its issue key?
When you change the issue type while keeping the issue in the same project, Jira generally keeps the existing issue key. Moving the issue to another project can affect its key, so check Jira’s confirmation details before submitting. If your team uses issue keys in links, release notes, or other systems, verify those references after the change.
Why can’t I see the Move option in Jira?
The Move action may be unavailable because your account lacks the necessary permission, or the project has restrictions. The interface can also differ depending on the Jira project setup. Ask a project administrator to confirm your access and whether moving issues is enabled. If the action is available elsewhere in your interface, use the project’s current Jira guidance to locate it.
Can I change multiple Jira ticket types at once?
Jira may let you use a bulk change operation to move several issues, provided your account has the right permissions and the project supports that action. Availability and prompts can vary. Try a small set of similar tickets first, then check their types, statuses, and fields before applying the operation to a larger group.
What should I check after changing an issue type?
Open the updated issue and confirm its type, status, and important fields. Then check whether it still appears on the right board and in relevant filters or reports. If the new type uses different required fields or workflow steps, update the ticket so teammates can understand and continue the work.
Conclusion
To change a Jira ticket type, open the issue, use More → Move, select the new type, and review any field or status prompts. The exact choices depend on your Jira project configuration and permissions.
Check the ticket after the change, especially if it appears on a board or feeds a report. If you are reclassifying many issues, test a small group first and make sure your team understands the new workflow.
That careful approach helps prevent a simple type change from creating confusion. When your team needs a Jira alternative with configurable workflows, built-in reporting, and flexible deployment options, ONES Project may be worth evaluating.