How to Change an Issue Type in Jira: A Step-by-Step Guide
Need to change an issue type in Jira? Follow the steps, handle field and status prompts, and avoid workflow surprises. Read now to learn how.
Choosing the wrong issue type can make a Jira issue follow the wrong workflow, show irrelevant fields, or disappear from the right team’s reports. Changing it sounds simple, but Jira may ask you to map fields, statuses, or values before it can complete the change. That extra step can be confusing, especially when you’re working with a customized project.
But here's the truth: you can usually change an issue’s type by moving it and selecting a different type. The exact prompts depend on your project configuration and permissions. Here’s a practical walkthrough, plus checks that help prevent lost information or workflow surprises.
How to Change an Issue Type in Jira
In many Jira projects, you change an issue’s type through the Move action rather than editing the type field directly. Use these steps for a single issue, and review Jira’s prompts before confirming.
Open the issue. Go to the Jira issue you want to change. Check its project, current type, status, and any fields that contain important details.
Open the issue actions. Select the three-dot menu or the issue’s available actions menu. Choose Move. The menu label or location can vary between Jira versions and project configurations.
Choose the destination project. If Jira asks you to select a project, keep the current project if you only want to change the issue type. Choose another project only when you intend to move the issue as well.
Select the new issue type. Choose the target type, such as changing a Task to a Bug or a Story to a Task. Jira may show a preview or additional steps before applying the change.
Review fields and statuses. Jira may ask you to map fields, select a status, or choose values that fit the new type. Check each prompt carefully, especially if the old and new types use different workflows or required fields.
Confirm the move. Review the summary, then complete the change. Reopen the issue afterward to confirm its type, status, fields, and links look right.
If you can’t find Move, you might not have the required project permission, or your project’s configuration may affect available actions. Ask a Jira administrator to check access and issue type settings.

What Changes When You Switch an Issue Type?
An issue type determines how Jira categorizes work and which configuration applies to it. The new type may use a different workflow, screen, set of required fields, or reporting category.
For example, a Bug may have fields for affected versions and severity, while a Task may not. Switching types can prompt you to map or complete fields so the issue fits its new setup.
Here’s why: changing the label alone may not be enough. If your team’s Story workflow includes review and acceptance steps, while a Task uses a simpler workflow, Jira may need you to select a valid status for the new type.
Check These Details Before You Change the Type
A quick review can prevent extra work after the switch. Start by checking whether the target type is available in the project and whether your account can move issues.
Workflow fit: Identify whether the new type uses different statuses or transitions. Consider whether the issue’s current status has a sensible equivalent.
Required fields: Check whether the destination type requires fields that the current issue does not have. Have the relevant values ready before you begin.
Subtasks and links: Review any child issues, linked work, or dependencies. Confirm that those relationships still make sense after the type changes.
Project permissions: If the action is missing or Jira blocks the move, ask an administrator to confirm your permissions and the project’s issue type configuration.
For example, changing a Story to a Bug may leave the team with a new required severity field. Adding a suitable value during the move is easier than discovering the omission during triage.
Change One Issue or Update Several?
For one issue, the Move action is usually the clearest route. It gives you a chance to review the destination type and resolve any field or status prompts before confirming.
If you need to change many issues, first check which bulk-edit options your Jira project allows. Bulk actions can save time, but different issue types may need different field values or workflow statuses.
For instance, a group of Tasks might all become Bugs, while another group needs to become Stories. Separate those groups and test the process on one issue from each group before applying a larger change.
Verify the Issue After the Change
After Jira completes the change, check the issue as a teammate would. Confirm the type, status, key fields, comments, attachments, and linked work are still present and useful.
Then check the issue in the places your team relies on, such as a board, queue, or report. A Bug may appear in a different board column or report category than a Story, even when the issue itself looks correct.
The best part? A short verification catches many common problems early. If a field is missing or the status looks wrong, contact your Jira administrator before the issue moves further through the workflow.
ONES.com as an Option for Flexible Issue Workflows
If your team is reviewing how it manages issue types and workflows, ONES.com offers a project management and knowledge management platform. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

ONES Project supports Jira-compatible workflows, custom workflows and fields, sprint management, automation, and built-in reporting. These capabilities can help teams shape work tracking around different issue needs, while reducing reliance on plugins for common project functions.
Core Capabilities
Workflow mismatch: Custom workflows let teams adapt work stages to their process, so issue types can follow more relevant paths.
Fields that don’t fit: Custom fields help teams capture information relevant to their work, such as a Bug’s severity or a Story’s acceptance details.
Jira migration concerns: Jira-compatible workflows can help teams preserve familiar ways of working while considering a Jira alternative.
Limited visibility: Built-in reporting helps teams monitor project progress without relying on a separate reporting add-on for every view.
Manual repetitive steps: Automation can handle selected routine actions, giving teams more time for issue review and delivery.
Sprint coordination: Sprint management supports teams that plan and track work in iterations.
Plugin complexity: A unified project management platform can reduce the number of plugins needed for common workflows and reporting needs.
Deployment constraints: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between its cloud and self-hosted versions.
Application Scenarios
A team with distinct work types: A software team may need Bugs, Stories, and Tasks to follow different stages. Custom workflows and fields can help represent each kind of work more clearly.
An organization with deployment requirements: A company that needs an on-premise or air-gapped environment can assess ONES Project alongside its existing workflow requirements. Teams can also start with the free plan, which supports up to 30 seats.
Teams seeking connected project and knowledge management: A group that wants project tracking and a knowledge base can evaluate ONES Project and ONES Wiki as separate products within the ONES.com platform. ONES Assistant provides AI capabilities within the platform.
Common Challenges When Changing an Issue Type
The Move Option Is Missing
Problem: You open the issue actions menu but can’t find Move. This may relate to your permissions or the project’s setup.
Solution: Ask a Jira administrator to check your project permissions and whether the target issue type is available in the project. Share the issue key and the type you need so they can investigate efficiently.
Jira Requests Field or Status Mapping
Problem: Jira presents choices you didn’t expect because the destination type has different fields or workflow statuses.
Solution: Read each prompt, choose values that preserve the issue’s meaning, and ask an administrator about unfamiliar options. Avoid selecting a value simply to get past the prompt.
Some Information Seems to Disappear
Problem: After the change, a field or value isn’t visible. The destination type may use a different screen or field configuration.
Solution: Check the issue’s available tabs and fields, then confirm the destination configuration with an administrator. If the information is still missing, investigate before editing other fields or changing the type again.
The Issue No Longer Appears on the Expected Board
Problem: The issue changed successfully but doesn’t show in the same board or report view.
Solution: Check the board’s filters, columns, and issue type settings. For example, a board may display Stories and Bugs but exclude Tasks, so the changed issue no longer matches its criteria.
FAQs About Changing Jira Issue Types
Can I change an issue type without moving the issue to another project?
Often, yes. When Jira opens the Move flow, you can usually keep the current project and select a different issue type. Review the project shown in the prompts before you continue. If your Jira setup doesn’t offer the action, check your permissions or ask an administrator whether the target type is available in that project.
Why can’t I edit the issue type directly?
Many Jira configurations treat a type change as a move because issue types can use different workflows, fields, and screens. The Move flow helps Jira collect any required choices during the change. Some projects may expose different controls, so the available options can vary. If you don’t see a suitable action, ask your administrator to check your project setup.
Will changing an issue type delete its comments or attachments?
A type change through Jira’s move process is intended to change how the issue is classified, but you should still verify the issue afterward. Check comments, attachments, links, and important field values. Project configuration and the actions you select can affect what appears after the move. If any important information is missing, contact a Jira administrator before making further changes.
Can I change the types of multiple Jira issues at once?
Jira may allow bulk operations, depending on your project, permissions, and configuration. Before changing a large group, separate issues that need different target types or field values. Test the process on a small number first, then check the results in the relevant board or report. If the bulk action isn’t available, an administrator can explain which options your Jira setup supports.
Conclusion
To change an issue type in Jira, open the issue actions, choose Move, select the target type, and carefully review any field or status prompts. Then verify the issue and its board or report placement.
But here's the truth: the change can affect more than the type label. Checking workflows, required fields, permissions, and linked work beforehand helps you avoid surprises and keep the issue useful to your team. If your current setup makes these changes difficult to manage, reviewing your workflow design or evaluating a Jira alternative may help.