How to Change an Issue Type in Jira: 5 Clear Steps That Work
Need to fix a Jira issue type? This guide to changing issue type in Jira shows 5 clear steps with Move—read now to preserve key details.
Changing an issue type in Jira can be quick, but choosing the wrong path may leave you with mismatched fields, a confusing workflow, or missing information. A Story may need to become a Bug, or a Task may belong under a different parent. If you simply create another issue and abandon the original, comments, history, and links can become harder to follow.
But here's the truth: Jira has a built-in Move process that can change an issue’s type while guiding you through project, workflow, and field choices. The labels and steps can vary slightly between Jira project types, so it helps to know what to check before you confirm.
Here’s how to change an issue type in Jira in five clear steps. You’ll also learn what can change during the process, how to fix common blockers, and when a project’s configuration needs attention.
How to Change an Issue Type in Jira: Five Steps
Open the issue and use Jira’s Move action to select a new issue type. Review any field or workflow prompts, then confirm the change. In most cases, you need permission to move issues and the new type must be available in the project.
-

Open the issue you want to update
Go to the Jira issue and check its key, current type, project, and important details. Confirm that you have the right issue before making a change, especially if several tickets have similar summaries.
For example, if APP-418 is a Task that should be a Bug, make sure you are changing that ticket rather than a linked ticket with a similar title.
-
Choose Move from the issue actions
Open the issue’s actions menu, often shown as More or an ellipsis, and select Move. Jira may place this action in a different spot depending on your interface and project type.
If you cannot find Move, check whether your account has the project permission to move issues. A Jira administrator can review permissions and project configuration if the action is unavailable.
-
Select the project and new issue type
In the Move wizard, select the current project if you only want to change the issue type. Then choose the intended type, such as changing a Task to a Bug or a Story to an Epic.
Jira may ask you to choose a destination project as well. Check that the target project supports the issue type you want. If the type is missing, an administrator may need to update the project’s issue type settings.
-
Review field and workflow choices
Jira can ask you to map fields when the old and new types use different screens or requirements. A Bug may require priority or environment details, while a Story may use acceptance criteria.
Review each prompt carefully. If Jira cannot carry a value across, choose an available option or make a note to restore that information after the change. The new type may also use a different workflow or status mapping.
-
Confirm the change and check the issue
Review the summary of the move and confirm it only when the project and issue type are correct. After Jira completes the process, reopen the issue and check its type, status, fields, comments, links, and history.
If the issue now has a different workflow or required fields, update those details before moving on. For example, add a reproduction step if a Task became a Bug and Jira’s Bug screen requires it.
How Jira Issue Types Work
An issue type tells Jira what kind of work a ticket represents. Common types include Epic, Story, Task, Bug, and Sub-task, though a project may use custom types such as Change Request or Support Request.
Issue types can affect which fields appear, which workflow applies, and how a ticket relates to other work. Changing a Task to a Bug can expose bug-specific fields, while changing a Story to a Sub-task can involve parent and hierarchy rules.
Here’s why: a type is more than a label. Think of it as a ticket’s route through the project. Two tickets may share a title, yet their required details and status transitions can differ because they represent different work.
What to Check Before Changing a Type
Before you start, confirm the intended type is available in the project and that you have permission to move the issue. If a team uses custom workflows or required fields, check whether those settings differ between the old and new types.
- Confirm the issue key and current project.
- Check that the destination type is available in the project.
- Review any required fields associated with the new type.
- Consider whether the new type changes the issue’s parent or hierarchy.
- Check whether dashboards, automation, or reports rely on the current type.
For example, a support team might use a custom “Customer Request” type with a required account field. Switching it to Bug could remove that field from the screen, so capture any important details before proceeding.
You might be wondering: do you need to create a replacement ticket instead? Usually, changing the existing issue is easier when you want its history and discussion to remain together. A new issue may be more suitable when the work itself is separate.
What Can Change After the Conversion
The issue’s type changes, but related settings may change too. Jira may apply a different workflow, display different fields, or ask you to map a status. The exact result depends on the project’s configuration and the destination type.
Consider a Story moving to Bug. The ticket may enter a Bug workflow, and the team may expect reproduction steps that were not required for Stories. If your project uses automation, a rule that reacts to issue type could also run after the change.
The best part? You can reduce surprises by checking the issue immediately afterward. Look at the activity history, linked issues, comments, status, and required fields. If a report no longer includes the ticket, check whether it filters by the old type.
Why the Move Option or New Type May Be Missing
If Move does not appear, your account may lack the required permission, or the project may restrict the action. Ask a Jira administrator to check the project’s permissions and issue type settings rather than trying to work around the restriction.
If the destination type is absent, it may not be enabled for that project. In a company-managed project, the issue type scheme controls which types are available. Team-managed projects have their own project settings, so the steps to add a type can differ.
Changing between parent and sub-task types can introduce additional restrictions. Jira may ask you to select a parent or resolve a hierarchy conflict. If the wizard blocks the change, check the issue’s parent-child relationships before trying again.
Issue Type Management Beyond Jira: ONES.com
ONES.com brings project management and knowledge management together in an AI-powered platform. ONES Project provides project management capabilities as a Jira alternative, while ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

For teams reviewing how they manage work types, workflows, and project information, ONES Project offers Jira-compatible workflows and configurable project processes. It is worth considering when you want project management options that include on-premise or air-gapped deployments.
Core Capabilities
- When teams need familiar Jira-style processes: Jira-compatible workflows help teams work with established practices while evaluating a Jira alternative.
- When project workflows need adjustment: Custom workflows let teams shape work transitions around their process, helping clarify how tickets move forward.
- When teams track different kinds of work: Custom fields support project-specific details, helping teams capture relevant information in their workflows.
- When delivery work follows sprints: Sprint management supports planning and tracking iterative work, keeping sprint activity within the project management environment.
- When teams need progress visibility: Built-in reporting gives teams reporting capabilities without making extra plugins the default requirement.
- When repeated actions take time: Automation supports routine project tasks, helping reduce manual steps in day-to-day work.
- When teams want fewer add-ons: Native capabilities can reduce reliance on plugins for supported needs, simplifying the project environment.
- When deployment requirements are strict: Cloud, On-Premise, Private Cloud, and Air-gapped deployment options let organizations choose an environment that fits their needs.
ONES.com offers a free plan for up to 30 seats. Its cloud and self-hosted versions have full feature parity, which can help teams evaluate deployment choices without giving up feature access in the self-hosted version.
Application Scenarios
A software team changing its project setup: A team that manages Bugs, Stories, and Tasks can assess whether configurable workflows and fields fit its processes. Jira-compatible workflows may help the team work with familiar patterns as it evaluates a Jira alternative.
An organization with restricted network requirements: A team that cannot use a cloud-only deployment can consider ONES.com’s On-Premise, Private Cloud, or Air-gapped options. Full feature parity between cloud and self-hosted versions gives the team deployment flexibility alongside project capabilities.
Common Challenges When Changing an Issue Type
The new type is not available
Problem: The Move wizard does not offer the type you need. Solution: Ask a project administrator to check whether that type is enabled for the project. Avoid choosing a different type just to get past the wizard, since that can create reporting and workflow problems.
Required fields are missing or incomplete
Problem: Jira asks for values that the old type did not require, or a value cannot be mapped. Solution: Review the prompts and fill in the new type’s required details. After the change, check the issue screen again for fields that need attention.
The issue has a different status afterward
Problem: The destination type uses a different workflow, so the issue does not retain the status you expected. Solution: Review the status choices in the wizard and confirm the resulting status after the change. Ask an administrator for help if the needed status is unavailable.
Reports or automation behave differently
Problem: A dashboard or automation rule filters by the old type, so the issue appears differently after conversion. Solution: Check project rules and report filters that depend on issue type. Update them if the new type should be included in the same view or process.
FAQs About Changing an Issue Type in Jira
Can I change a Jira issue type without creating a new issue?
Yes. In many Jira projects, you can use the issue’s Move action and select a different type in the wizard. This changes the existing issue rather than requiring you to start over. Check the issue afterward, since the new type may use different fields, workflows, or status rules.
Why can’t I see the Move option in Jira?
The Move action may be hidden because your account lacks the required permission, or the project may restrict moving issues. Its location can also vary between Jira interfaces. Check the issue actions menu first, then ask a Jira administrator to review your permissions and the project’s configuration.
Will changing an issue type delete comments or history?
Changing the type through Jira’s Move process updates the existing issue, so its activity and discussion remain associated with that issue. However, you should still review the issue afterward. Fields, workflows, status, and reporting behavior can change, and some details may need to be mapped or entered again.
Can I change a Jira issue into a sub-task?
Sometimes, but the change can involve hierarchy rules and parent-child relationships. Jira may ask you to select a parent or resolve a conflict before continuing. If the wizard will not proceed, check whether the issue already has a parent or children, then ask an administrator to review the project’s hierarchy settings.
Conclusion
To change an issue type in Jira, open the issue, choose Move, select the project and new type, review Jira’s prompts, and confirm the change. Then check the fields, status, links, history, automation, and reports that matter to your team.
Changing the type can feel risky when project settings differ, but a quick review before and after the Move process can prevent most surprises. If Jira blocks the change, check permissions, project settings, and hierarchy rules before creating a replacement ticket.