How to Change an Issue Type in Jira: 5 Simple Steps Safely
Need help with jira change type of issue? Follow 5 simple steps to protect fields, workflows, and reports—read now.
Changing an issue type in Jira can be straightforward, but choosing the wrong type may disrupt fields, workflows, or reporting. A task converted into a bug, for example, might need details that weren’t required before.
That’s why a quick change without checking the issue’s fields and project settings can create extra cleanup. But here’s the truth: you can change an issue type safely by using Jira’s Move action, reviewing the destination type, and checking the result afterward. I’ll walk you through five steps, explain what to check before you confirm, and cover common problems that can block the change.
How to Change an Issue Type in Jira: 5 Steps
In Jira, use the issue’s Move action to change its type while keeping it in the same project. Review any field changes Jira requests before confirming.
- Open the issue. Go to the Jira issue you want to update. Check its current project, issue type, status, and key details before making changes.
- Open the Move action. Select the issue’s
More menu, then choose Move. The exact menu placement can vary with your Jira version and project configuration.
- Keep the current project. If Jira asks where the issue should go, select the same project. Then choose the new issue type, such as Bug, Task, or Story.
- Review the field changes. Jira may show fields that are unavailable for the new type or required fields that need values. Map or complete the requested information carefully.
- Confirm and verify. Review the summary, project, and destination type, then confirm the change. Reopen the issue and check its fields, status, comments, and relevant links.
Here’s why the field review matters: issue types can use different screens and required fields. For example, changing a Task to a Bug may prompt you to add environment details or a bug-specific priority.

What Changes When You Switch an Issue Type?
An issue type identifies the kind of work Jira tracks, such as a bug, task, story, or sub-task. The type can determine which fields appear, which workflow applies, and how the work is grouped in reports.
Changing the type doesn’t necessarily change the issue’s project or key. However, fields and workflow behavior can differ between types. A Story might show an Epic Link or parent relationship, while a Bug may have fields for reproduction steps.
Consider a task that turns out to be a product defect. Changing it to a Bug can make it appear in bug-focused reports, but Jira may ask you to complete fields the Task type did not require.
Check These Details Before You Make the Change
Confirm the New Type Fits the Work
Pick a type that reflects how your team plans, assigns, and reports the work. If the issue describes a defect that needs investigation, Bug may be more suitable than Task. For a planned feature, Story could be the better fit.
You might be wondering: should you change the type or create a new issue? Change the existing issue when its history, comments, and links should remain together. Create a separate issue when the work has become a distinct piece of work that needs its own tracking.
Review the destination type’s required fields before starting. A project administrator can tell you whether the type has its own workflow, screens, or validation rules.
For example, if a new type requires a component or acceptance criteria, be ready to enter those values during the change. Missing a required field can prevent Jira from completing the move.
Look for Parent and Sub-Task Relationships
Issue types can sit at different levels in a project’s work hierarchy. A sub-task, for instance, depends on a parent issue, while an Epic may organize larger work.
Check parent links and hierarchy restrictions before changing types. Jira may prevent a change when the new type cannot occupy the issue’s current position in the hierarchy.
How to Verify the Change and Fix Common Problems
After confirming the change, open the issue again and check that the new type appears beside the summary. Then review required fields, status, assignee, priority, and parent relationships.
Also check a relevant board or report. A Bug may appear in a bug-focused filter, while a Story may be grouped differently. If the issue disappears from a board, the board’s filter may exclude its new type.
If Jira blocks the change, read the on-screen message first. It may point to a missing required field, a project configuration rule, or a hierarchy restriction. For example, a sub-task may not be convertible to a standard issue type while retaining its existing parent relationship.
When the error isn’t clear, ask a Jira administrator to review the project’s issue type scheme, field configuration, workflow, and permissions. Avoid trying several type changes in a row; each attempt can make it harder to understand which rule is causing the problem.
Jira Issue Type Changes: Common Challenges
- The Move option is missing. Your permissions or project configuration may not allow the action. Ask a Jira administrator to confirm your access and the project’s available operations.
- Jira asks for fields you don’t recognize. The destination type may require additional information. Complete the fields with accurate values, or ask the project owner what belongs there.
- The new type isn’t available. The project’s issue type scheme may not include it. An administrator can check whether the type is enabled for that project.
- The change affects a parent or child link. The selected type may not fit the issue’s current hierarchy position. Confirm the intended relationship with your team before proceeding.
- The issue no longer appears on a board. The board may filter by issue type or another field. Review its filter criteria, or ask a board administrator to check them.
ONES.com Solution for Jira-Style Issue Management

Value Proposition
ONES.com brings project management and knowledge management together in one unified platform, with ONES Project for project work and ONES Wiki for team knowledge. If you need a Jira alternative, ONES Project offers Jira-compatible workflows and project controls, including options for teams that require on-premise or air-gapped deployments.
ONES Project and ONES Wiki are sold separately. You can choose the project management capabilities that fit your work without treating the knowledge base as a required add-on.
Core Capabilities
- Issue type and workflow needs: Teams can use custom workflows and fields, helping them represent different kinds of work with clearer steps and information.
- Jira workflow continuity: Jira-compatible workflows can help teams preserve familiar ways of handling work while moving to another platform.
- Manual status updates: Automation can reduce repetitive workflow tasks, so teams spend less time updating issues by hand.
- Limited progress visibility: Built-in reporting gives teams a way to review work and project progress without relying on a separate reporting add-on.
- Sprint planning overhead: Sprint management supports teams that plan and track work in iterations.
- Plugin dependence: Native capabilities across workflows, reporting, custom fields, and automation can reduce the need for extra plugins.
- Restricted hosting requirements: Cloud, on-premise, private cloud, and air-gapped deployments give organizations deployment options for different environments.
- Feature differences between hosting models: ONES.com offers feature parity between its cloud and self-hosted versions, helping teams evaluate deployment without planning around a reduced feature set.
Application Scenarios
A software team moving from Jira can evaluate ONES Project when it wants to retain familiar workflow patterns while using native project features. For example, a team could configure work types and statuses for bugs, tasks, and sprint work, then use built-in reporting to review progress.
An organization with restricted network requirements can consider an on-premise, private cloud, or air-gapped deployment. Its project team can manage work in ONES Project, while a team that also needs a knowledge base can separately consider ONES Wiki.
ONES.com offers a free plan for up to 30 seats. The available deployment choices and feature parity may be useful considerations when your team compares Jira alternatives, especially if hosting requirements or plugin reliance affect that decision.
FAQs
Can I change an issue type without changing its project?
Yes. In the Move flow, keep the current project selected and choose the destination issue type. Jira may still ask you to map or complete fields because the new type can use different requirements. Before confirming, check that the project and type shown in the final review match your intentions.
Will changing the issue type delete comments or history?
The Move action changes the issue’s type and may request field updates; it is not the same as creating a new issue. Review the issue after the change to confirm its comments, history, and links are still present. If preserving the full history is critical, check your project’s behavior with an administrator before proceeding.
Why can’t I see the Move option in Jira?
The option may be unavailable because of your permissions, the project’s configuration, or the way your Jira instance presents issue actions. Ask a project or Jira administrator to check your access and whether the action is enabled. You can also check whether the issue view has placed the action under a different menu.
Can I change a sub-task into a Story or Bug?
It depends on the project’s hierarchy rules and Jira configuration. A sub-task is attached to a parent, while a Story or Bug is generally a standard issue type. Jira may prevent the conversion or require a different parent relationship. Check the on-screen message and ask an administrator to explain the available options.
What should I do if the issue disappears from my board after the change?
First, confirm the issue still exists and has the expected new type. Then check whether the board’s filter includes that type and whether other conditions, such as status or assignee, exclude the issue. A board administrator can review its filter and update it if the changed issue type should appear.
Conclusion
Changing an issue type in Jira usually involves opening the issue’s Move action, keeping the project, selecting a new type, and reviewing any field changes. Take a moment to check hierarchy rules and required fields before confirming.
If Jira blocks the change or the issue behaves differently afterward, inspect the project configuration and board filters with an administrator. A careful review can help you keep work history intact and make sure the issue lands in the right workflow.