Jira Issue Type Change: A Step-by-Step Guide for Admins
Worried about losing issue data? This admin guide to jira issue type change shows how to map fields and verify results. Read now to change issues safely.
Changing an issue type in Jira can look like a small edit, but it may affect fields, workflow steps, and reporting. Choose the wrong type, and the issue could lose information or land in a status that does not fit its new workflow. That makes a quick fix feel risky, especially when you are working with a live project or several linked issues. But here's the truth: Jira provides a guided way to move an issue to another type, and a little preparation can prevent most surprises. Here’s how to make the change, check what Jira will ask you to map, and verify the result afterward. I’ll also explain what to review when you are updating several issues or planning broader workflow changes.
How to change an issue type in Jira
In many Jira projects, you change an existing issue’s type through the Move action. This guided process lets you select a new type and review any required field or status changes before confirming.
- Open the issue. Check its current type, status, fields, comments, and relationships. Note any details that are important to preserve.
- Choose the Move action. Open the issue’s action menu, often labeled More, and select Move. The menu wording can vary by Jira version and project configuration.
- Keep the same project, if that is your goal. Select the current project as the destination. A move can also change the project, so confirm this choice before continuing.
- Select the new issue type. Choose the target type, such as changing a Task to a Bug. If the type is unavailable, an administrator may need to review the project’s issue type scheme.
- Review the change details. Jira may ask you to map statuses or enter values for fields required by the new type. Read each prompt and supply suitable information.
- Confirm the move. Check the destination project and type again, then complete the guided process.
- Verify the updated issue. Confirm the new type, status, required fields, comments, and relationships. Check that the issue appears in the expected board or queue.
For example, when changing a Task to a Bug, Jira may ask you to choose a Bug workflow status or fill in fields required for bugs. The prompts depend on your project configuration.

Check access and project configuration first
If you cannot see the Move action or the target type, check your permissions and project setup before trying another route. Jira typically requires permission to browse the project and move issues. Your administrator can confirm whether your account has the required access.
The target issue type must also be available to the project. Administrators manage which types a project can use through its issue type scheme. For example, a project configured only for Tasks and Subtasks may not offer Bug as a destination.
Here’s why this matters: changing an issue’s type does not automatically make every type available everywhere. If the type is missing, ask an administrator to check the project configuration instead of assuming the issue itself is broken.
Understand what can change along with the type
Issue types can use different workflows, screens, and fields. A Bug might require severity and reproduction details, while a Task might use a simpler set of fields. During the change, Jira can prompt you to address differences between the current and target types.
Status mapping deserves particular attention. If the old workflow has a status that the new workflow does not use, Jira may ask you to select a valid destination status. Choose one that accurately describes the work. For example, an issue marked “In Review” should not automatically become “To Do” unless the team has actually reopened it.
Afterward, review relationships and team views. Check parent-child links, board filters, sprint placement, and any reports that depend on issue type. A type change can alter where an issue appears, even when its key and history remain available.
Choose the right type before making the change
Issue types describe the kind of work an issue represents. Common examples include Epic, Story, Task, Bug, and Sub-task, though available types vary by project. A status such as “In Progress” describes work state; it is not an issue type.
That distinction helps prevent unnecessary changes. If a Task is simply waiting for review, changing its type to Bug will not fix the status. Adjust the status through the workflow instead, if your permissions and workflow allow it.
Sub-tasks have a parent-child relationship with another issue, so changing to or from a Sub-task can involve extra restrictions. Before attempting that conversion, check the target project’s hierarchy rules and confirm where the issue should sit. If Jira blocks the change, ask an administrator to review the relationship and available conversion options.
Plan carefully when changing multiple issues
For a single issue, Jira’s guided Move process is usually straightforward. For a group, test the change on one representative issue first. That trial can reveal required fields, status mapping, or unexpected effects before you repeat the process.
When handling a batch, define the intended result clearly. For example, list which issues should become Bugs, which should stay Tasks, and what statuses make sense afterward. Ask a project administrator to confirm whether Jira’s bulk operations support the change in your setup. Available actions can depend on project type, permissions, and configuration.
After a batch change, check a sample from each affected group. Compare their types, statuses, required fields, and board visibility against the intended outcome. If a group behaves differently from the test issue, pause and investigate before continuing.
When broader workflow changes need attention: ONES.com
When issue-type changes point to a larger need for clearer project workflows, ONES.com offers project management and knowledge management capabilities in one platform. ONES Project is its project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

Core capabilities
- Disconnected project practices: ONES Project supports Jira-compatible workflows, helping teams carry familiar issue processes into a new environment.
- Workflow changes that need administration: Custom workflows let teams shape issue progress around their actual review and delivery steps.
- Fields that do not capture enough context: Custom fields help teams record details relevant to their work, so issues can carry useful context through the process.
- Limited progress visibility: Built-in reporting helps teams review project progress without relying on a collection of separate reporting add-ons.
- Sprint planning needs: Sprint management supports teams organizing planned work into development cycles.
- Repeated manual actions: Automation can handle eligible routine steps, reducing repetitive work for project teams.
- Too many separate products: ONES.com brings project and knowledge management under a unified platform, while ONES Project and ONES Wiki remain separately sold products.
- Deployment constraints: Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment. The self-hosted version has feature parity with the cloud version.
Application scenarios
A team reviewing issue types across several projects could use custom workflows and fields to standardize how requests move from intake to delivery. Built-in reporting could then help project leads see progress across that process.
A team in a restricted network environment could consider an Air-gapped deployment. A team already working with Jira-compatible workflows could evaluate ONES Project as a Jira alternative, with fewer separate plugins needed for capabilities such as reporting and automation.
ONES.com offers a free plan for up to 30 seats. Before choosing a platform, map the issue types, workflows, permissions, and deployment requirements your team actually needs.
Common challenges and practical fixes
- The Move action is missing: Your account may not have the required permission, or the project may use a configuration that changes the available actions. Ask an administrator to check your access and project setup.
- The target type is not listed: The project may not allow that issue type. Have an administrator review the issue type scheme before attempting the change again.
- Jira requests field values: The new type may require information the old type did not. Enter accurate values, or ask the project owner which choice matches team practice.
- The status does not fit: The two issue types may use different workflows. Select a status that reflects the issue’s actual progress, then confirm the result after the change.
- The issue disappears from a board: A board filter or project view may exclude the new type. Check the board’s criteria and ask its administrator to update them if needed.
Frequently asked questions
Can I change an issue type without changing projects?
Often, yes. In the Move process, select the issue’s current project as the destination and choose the new issue type. Jira may still ask you to map a status or complete fields required by the target type. If the option is unavailable, check your permissions and ask an administrator whether the target type is enabled for that project.
Why can’t I see the issue type I need?
The target type may not be included in the project’s issue type scheme, or your account may lack permission to move the issue. It is also possible that the project configuration limits the types available. Ask a Jira administrator to check the scheme and your access. Once the type is available, reopen the issue and try the guided Move process again.
Will changing an issue type delete its comments or history?
A type change through Jira’s Move process is intended to update the issue’s type, with Jira guiding you through relevant conversion details. Still, check the issue after the change. Confirm that its comments, status, fields, and relationships look right. If the issue contains critical history or complex links, ask your administrator to review the plan before making the change.
Can I change the issue type for several issues at once?
Bulk options depend on your Jira setup, permissions, and the actions available for the project. Test the intended change on one issue first, then ask an administrator whether a suitable bulk operation is supported. For a larger group, define the target types and status outcomes in advance. Afterward, check examples from each group to catch configuration differences early.
Conclusion
Changing an issue type in Jira usually means using the guided Move action, selecting the right destination, and reviewing any field or status prompts. Check permissions and project configuration first, especially when the target type is missing.
Then verify the result: confirm the issue’s type, status, fields, relationships, and visibility in team views. A careful test before a larger update can prevent confusing workflow changes. When type changes reveal broader process needs, review whether your current project setup supports the way your team plans, tracks, and completes work.