How to Change an Issue Type in Jira: Step-by-Step Guide
Need to convert a Jira issue safely? Learn how changing issue type in Jira affects fields and workflows—read now for the step-by-step guide.
Changing an issue type in Jira can be simple, but the wrong change may affect fields, workflows, and parent-child relationships. A task might need to become a bug, or a story may need to become an epic. If you choose the wrong destination type, Jira may ask you to map fields or may place the issue in a different workflow.
That can leave you with missing details, an unexpected status, or a broken link to a parent issue. The fix is to check the destination type and review Jira’s prompts before confirming.
Here’s how to change an issue type safely, what to check first, and how to verify the result afterward. I’ll also cover what to do when Jira doesn’t offer the type you need.
How to Change an Issue Type in Jira
In most Jira projects, you change an issue type through the issue’s Move action. Select the new type, review any field or status mapping, and confirm the change.
- Open the issue. Go to the issue you want to change and confirm you have permission to edit or move it.
- Open the action menu. Select More or the issue’s action menu, then choose Move. The label and menu location can vary by Jira version and project type.
- Keep the current project. If Jira asks where to move the issue, select the same project unless you also intend to transfer it.
- Choose the destination issue type. Select the type that matches the work, such as changing a task to a bug or a story to an epic.
- Review the change details. Jira may ask you to map fields, choose a status, or resolve parent and child relationships. Check each prompt before proceeding.
- Confirm the change. Complete the wizard, then reopen the issue and verify its type, status, fields, and relationships.
But here's the truth: the available choices depend on your project configuration and permissions. If the type you want is missing, check with a Jira administrator before trying another route.

What to Check Before You Change the Type
Start by confirming that the new type is appropriate for the work. A bug usually describes a defect, while a story or task describes planned work. An epic typically groups related work rather than representing one small action.
Next, check whether the target type is available in the project. Jira project settings and issue type schemes control which types can appear. For example, a project configured for tasks and bugs may not offer stories until an administrator updates its configuration.
Also check your access. You may need permission to move issues, and a project administrator may need to adjust configuration. If the Move action is absent, that doesn’t necessarily mean Jira cannot change the type.
Review Fields and Status Mapping Carefully
When the destination type uses different fields, Jira may show a mapping step. A field used by the old type might not exist on the new one, while the destination type may require information the issue doesn’t currently have.
For example, changing a task into a bug could require a priority or environment value. If Jira asks you to map a field, select the closest valid destination or provide the missing value when appropriate.
Here's why: the issue’s workflow can also change with its type. Jira may ask you to choose a status that exists in the destination workflow. Check that the selected status accurately reflects the work, rather than simply accepting the first available option.
Understand Parent, Child, and Epic Relationships
Issue types can represent different levels of work. Changing a story into an epic, for instance, may affect how child issues are organized. Jira can prompt you to resolve relationships that don’t fit the new type.
Imagine a story with subtasks that needs to become an epic. Before confirming, check whether Jira will preserve those subtasks or require another relationship. If the issue belongs to a parent, inspect that connection too.
The best part? A quick review before confirmation can prevent cleanup later. If the relationships are unclear, ask the project owner or administrator how your team expects work to be structured.
Verify the Issue After the Change
After the change, check the issue type icon or type field, then review its key details. Confirm that the summary, description, priority, assignee, and other important fields remain correct.
Check the status and workflow actions as well. A new issue type may use a different workflow, so the available transitions can change. Try the next expected action only after confirming the issue is in the right status.
Finally, inspect parent and child links and review the issue activity. For a high-impact change, ask a teammate to confirm the issue appears correctly in the project board or backlog.
Changing Issue Types at Scale: ONES.com
If your team regularly adjusts work types, clear workflows and consistent fields can make those changes easier to manage. ONES.com combines project management and knowledge management in one platform, with ONES Project for project management and ONES Wiki for knowledge management. They are sold separately.

ONES Project is a Jira alternative with Jira-compatible workflows. If your team is evaluating a different setup, compare how each platform handles issue types, permissions, and workflow changes against your actual process.
Core Capabilities
- Complex workflow changes → Custom workflows → Define process steps to match how your team handles tasks, bugs, and other work types.
- Inconsistent issue details → Custom fields → Capture the information your team needs for each type without relying on one set of fields for every issue.
- Unclear progress → Built-in reporting → Review project status and work trends without assembling separate reports.
- Sprint planning friction → Sprint management → Organize work into sprints and track progress through the team’s delivery cycle.
- Repeated manual steps → Automation → Reduce routine work with rules for common project actions.
- Dependence on extra extensions → Native capabilities → Use built-in project features and reduce reliance on plugins where they meet your needs.
- Deployment constraints → Cloud, On-Premise, Private Cloud, and Air-gapped options → Choose an environment that fits your organization’s operational requirements.
- Migration concerns → Feature parity between cloud and self-hosted versions → Evaluate deployment choices without giving up feature availability between those versions.
Application Scenarios
A software team refining its issue workflow: A team that often reclassifies tasks as bugs can define custom workflows and fields around its process. That makes the expected details and next steps easier to follow.
An organization with deployment requirements: A team that cannot use a public cloud environment can evaluate ONES Project’s self-hosted deployment options, including On-Premise, Private Cloud, and Air-gapped deployments.
A team moving from Jira: A team considering a Jira alternative can assess Jira-compatible workflows, built-in reporting, sprint management, automation, and its need for plugins before deciding whether the platform fits.
Common Challenges When Changing Issue Types
- The destination type is missing. Your project may not include that type in its configuration. Ask a Jira administrator to check the project’s issue type scheme and permissions.
- The Move action is unavailable. Your account may lack the required permission, or the project’s interface may place the action elsewhere. Check your access and menu options with an administrator.
- Jira asks for field values you don’t have. The destination type may require fields that were optional or unavailable before. Confirm the right values with the issue owner instead of guessing.
- The new status seems wrong. The target type may use a different workflow. Review the available status options and choose one that matches the issue’s actual progress.
- Relationships become unclear. A type change can affect parent or child links. Inspect the issue hierarchy before confirming and repair relationships afterward if Jira prompts you.
FAQs About Jira Issue Type Changes
Can I change an issue type without moving it to another project?
Usually, yes. In the Move wizard, you can select the same project and choose a different issue type. Jira uses the Move action for this kind of change in many configurations, even when you are not transferring the issue elsewhere. If the option is unavailable, check your permissions and ask a project administrator whether the destination type is enabled.
Why can’t I see the issue type I need?
The project may not allow that type, or your account may not have permission to move the issue. Jira project configuration determines which issue types are available. Ask a Jira administrator to check the project’s issue type scheme and your access. Avoid changing the project or creating a replacement issue just to work around a missing option.
Will changing the type delete the issue’s comments or history?
A type change normally updates the existing issue rather than creating a new one, so its activity history and comments remain associated with it. However, fields and workflow details can vary with the destination type. After the change, review the issue’s details and activity to confirm important information is still visible and the issue follows the expected workflow.
Can I change an epic into a story or task?
Jira may allow a change between types, but hierarchy rules and relationships can affect what happens next. An epic may have child issues, and the target type may not support the same relationships. Review Jira’s prompts before confirming, and check with your project administrator if you are unsure how the team expects that work to be organized.
Conclusion
Changing a Jira issue type is usually a matter of opening the issue’s action menu, selecting Move, and choosing the destination type. The important work happens in the review: check fields, workflow status, permissions, and issue relationships before confirming.
If the right type is missing or the prompts are unclear, pause and ask a Jira administrator rather than guessing. With a careful check before and after the change, you can keep the issue accurate and your team’s work easy to follow.