Changing an issue type in Jira sounds simple until the wrong workflow, fields, or permissions get in the way. A Story may need to become a Bug, while an Epic may have been created under the wrong project. One careless change can hide fields, remove required information, or disrupt reporting.
That uncertainty creates extra cleanup for your team. You may also wonder whether comments, attachments, links, and status history will survive the change.
But here's the good news: Jira provides a reliable way to correct issue types. Follow the right steps, check the project configuration, and review the result afterward. This guide shows you exactly how to change an issue type safely.
How to Change an Issue Type in Jira
To change an issue type in Jira, open the issue, select the issue actions menu, choose “Move,” select a new issue type, review any required field changes, and confirm the move. Jira may call this action “Move” because changing the issue type can also affect the project and workflow.
Step 1: Open the Jira issue
Find the issue you want to update and open its full view. You cannot usually change the type from every compact issue list.
Check the issue key, project, summary, and current type before continuing. This quick check prevents changes to the wrong item.
Step 2: Open the issue actions menu
Look for the three-dot menu near the issue title. In some Jira layouts, the option appears under “More” or “Actions.”
Choose Move. If you cannot see this option, your account may lack the required permission, or the project may restrict issue moves.
Step 3: Select the destination project
Jira may ask where the issue should live. Keep the current project if you only want to change the issue type.
Choose another project only when the issue belongs elsewhere. Moving between projects can change available fields, workflows, screens, and security settings.
Step 4: Choose the new issue type
Select the correct destination type, such as Bug, Task, Story, Epic, or a custom type.
Read the available choices carefully. A custom type may look similar to a standard type while following a completely different workflow.
Step 5: Review field changes
Jira displays a review screen when the new type uses different fields. Some fields may become unavailable, while others may become mandatory.
Enter missing values before continuing. For example, changing a Task to a Bug may require severity, environment, or reproduction details.
Step 6: Confirm the change
Review the project, new issue type, and field values. Then select Move or Confirm.
Jira should preserve the issue key in most same-project changes. Comments, attachments, links, and activity history generally remain connected to the issue.
Step 7: Verify the result
Return to the issue and confirm the new type appears beside the title. Check the status, available actions, fields, and workflow buttons.
Try the next expected action. If the issue is now a Bug, confirm that the bug workflow and required fields behave as expected.
What Changes When You Switch an Issue Type?
Changing an issue type can affect more than the label beside an issue title. Jira connects issue types with schemes, workflows, screens, fields, and reporting behavior.
| Area | Possible effect |
|---|---|
| Fields | Some fields may disappear, while others may become required. |
| Workflow | The issue may receive different statuses or transition actions. |
| Screen layout | The create, edit, or view screen may show different fields. |
| Reports | Charts, filters, and dashboards may group the issue differently. |
| Hierarchy | Parent and child relationships may need review, especially with Epics. |
| Automation | Rules that watch issue types may trigger or stop triggering. |
Here's why: Jira uses the issue type as a configuration signal. A Bug can trigger different automation from a Story, even when both belong to the same project.
For example, a rule might notify the quality team when an issue becomes a Bug. Changing a Bug into a Task could stop that notification and alter dashboard counts.
Same-project changes
A same-project change is usually the simplest option. The issue keeps its project context, while Jira applies the destination type’s configuration.
This approach works well when a team created an issue under the wrong category. For example, you can change a wrongly created Task into a Story without relocating it.
Cross-project changes
Moving an issue to another project adds more risk. The destination project may use different workflows, permission rules, screens, or custom fields.
Review the destination project first. A type that exists in your current project may not exist in the other project.
Hierarchy changes
Special issue types can have structural rules. Changing an Epic into another type may affect child issues or planning relationships.
Check parent links, child issues, and board visibility after the change. This matters most when your team uses Advanced Roadmaps or similar planning features.
Jira Cloud and Jira Data Center Differences
The general process is similar across Jira Cloud and Jira Data Center. The menu labels, permission names, and configuration screens can differ.
Jira Cloud
In Jira Cloud, open the issue’s three-dot menu and look for Move. The option may appear under additional actions depending on your interface and project settings.
Cloud administrators manage issue types through project settings and global settings. Team-managed projects can have simpler, project-specific configurations.
Jira Data Center
Jira Data Center may use a more traditional administration layout. The move screen can expose additional mappings for fields and workflows.
Administrators should check the issue type scheme, field configuration, and workflow scheme before changing large groups of issues.
Team-managed and company-managed projects
Team-managed projects control more settings within the project itself. Company-managed projects often inherit centralized schemes managed by Jira administrators.
You might be wondering: why can one project change types easily while another blocks the option? The answer usually involves project type, permissions, and scheme configuration.
Permissions and Configuration Checks
Jira may hide or reject the move action when your account lacks the right permissions. The most common requirement is the Move Issues project permission.
Check your permission
Ask a Jira administrator to review the project permission scheme. Your account may be able to edit issues without being allowed to change their project or type.
These permissions are separate because moving an issue can affect ownership, security, workflow behavior, and reporting.
Check the issue type scheme
The destination type must be available in the project’s issue type scheme. If it is missing, an administrator must add it before you can use it.
For example, a project may support Story and Bug but exclude Epic. Selecting Epic will be impossible until the scheme changes.
Check field configuration
Required fields can prevent a successful change. Jira may ask you to enter values that the original issue never needed.
Review fields such as priority, component, environment, acceptance criteria, or severity. Complete meaningful values instead of adding placeholders.
Check workflow compatibility
The new type may use a workflow with different statuses. An issue currently in “In Review” could require a different status after the change.
Review the status after confirmation. If the issue appears in an unexpected state, ask an administrator to inspect the workflow mapping.
Changing Several Jira Issues at Once
For a few issues, individual changes are safer. For dozens or hundreds, Jira’s bulk change feature can save significant time.
But here's the truth: bulk changes amplify mistakes. A wrong filter can update unrelated issues across several teams.
Use a narrow search
Create a precise JQL search before starting. For example:
project = WEB AND issuetype = Task AND status = Open
Review the returned issues manually. Confirm the project, current type, status, and team ownership before selecting the bulk action.
Start with a small group
Test the change on two or three issues first. Check fields, workflow behavior, reports, and automation after the test.
The best part? A small test reveals configuration problems before they affect an entire backlog.
Complete the bulk move
Select the issues, choose the bulk action, and select the move option. Jira may guide you through project, type, field, and confirmation screens.
Keep the selection narrow if different issues need different field values. A single bulk operation works best when every issue follows the same mapping.
Review the results
Search for the old issue type and confirm the expected issues no longer appear. Then search for the new type and review the updated group.
Check dashboards and saved filters afterward. Bulk changes can alter counts immediately.
ONES.com as a Jira Alternative for Issue-Type Workflows
ONES.com is a project management platform that can support teams seeking structured issue tracking beyond Jira. It brings planning, development, collaboration, and reporting into one workspace.
It can be useful when your team wants clearer work categories without managing complex Jira schemes. You can evaluate the platform against your workflow before considering a migration.
Capabilities worth evaluating
- Work item management: Organize tasks, defects, requests, and product work in structured spaces.
- Custom workflows: Define statuses and transitions that match your team’s approval process.
- Role-based permissions: Control who can create, edit, move, or approve work items.
- Product planning: Connect requirements, releases, priorities, and delivery milestones.
- Development integration: Link engineering activity with planning and issue progress.
- Team collaboration: Keep discussions, updates, and decisions connected to the relevant work.
- Reports and dashboards: Track progress, workload, priority, and delivery trends.
- Cross-team visibility: Give product, engineering, quality, and leadership a shared view of progress.
For example, a product team could classify a customer request, send it through review, and connect it to a release plan.
Let me explain: the right platform depends on your team’s workflow complexity, migration needs, integrations, and administration capacity.
Best Practices Before Changing an Issue Type
A careful change takes only a few minutes. A careless change can create weeks of reporting and workflow confusion.
Confirm the reason for the change
Ask whether the issue truly needs a new type. Sometimes a label, component, priority, or custom field solves the problem without changing the issue structure.
For example, use a component for “Mobile” when the work remains a Story. Use a new issue type when the workflow or reporting needs are genuinely different.
Capture important details
Review the issue before moving it. Record key values such as acceptance criteria, severity, affected version, and linked work.
This is especially useful when the destination type does not display every field from the original type.
Check automation rules
Search for automation that uses the current or destination issue type. Rules may assign people, update fields, send notifications, or transition issues.
A type change can trigger a rule immediately. Make sure the resulting action is intentional.
Review board and filter behavior
Boards and filters often use issue type conditions. A changed issue may vanish from a board if its filter excludes the new type.
Check team boards, dashboards, saved filters, and reports after completing the change.
Communicate the change
Tell relevant teammates why the issue changed. A short comment can prevent confusion during planning or stand-up meetings.
For example, write: “Changed from Task to Bug because testing confirmed unexpected behavior.”
Common Challenges
The Move option is missing
Problem: You can edit the issue, but Jira does not show the move action.
Solution: Ask an administrator to check the Move Issues permission and confirm that the destination type exists in the project scheme.
Jira rejects the change because of required fields
Problem: The new issue type requires information the current issue does not have.
Solution: Add accurate values during the move. Ask an administrator whether the field should remain mandatory for that type.
The issue disappears from a board
Problem: The issue no longer appears on a board after its type changes.
Solution: Review the board filter and quick filters. The new type may be excluded from the board’s JQL.
Automation behaves unexpectedly
Problem: A notification, assignment, or transition happens after the type change.
Solution: Inspect automation conditions that reference issue types. Update the rule if the new behavior does not fit your process.
Parent or child links look wrong
Problem: Hierarchy relationships change after converting an Epic or another structured type.
Solution: Review parent links and child issues manually. Restore valid relationships or involve your Jira administrator.
FAQs
Can I change a Jira issue type without creating a new issue?
Yes. Jira’s Move action can change the issue type while keeping the existing issue record. In many same-project changes, the issue key remains unchanged. Comments, attachments, links, and activity history generally stay connected. Review the issue afterward because fields, workflow actions, and board visibility may change.
Why can’t I change the issue type in Jira?
The most common reasons are missing Move Issues permission, an unavailable destination type, or project configuration limits. Required fields can also block the operation. Ask an administrator to check the permission scheme, issue type scheme, field configuration, and workflow mapping.
Will changing the type delete comments or attachments?
Changing the type normally does not delete comments or attachments. However, some fields may no longer appear under the new type. Review important information after the change, especially when converting between standard and custom issue types.
Can I change multiple Jira issues together?
Yes. Jira supports bulk changes when your account has the required permissions. Use a narrow JQL search, test the process on a small group, and review the results afterward. Bulk changes work best when every selected issue needs the same destination type and field treatment.
Does changing an issue type affect reports?
It can. Reports, dashboards, boards, and saved filters may group or display issues by type. After changing an issue, check the relevant filters and charts. If the issue disappears, the board or report may exclude the new type.
Can I undo a Jira issue type change?
Jira does not always provide a simple undo button for a type change. You can usually repeat the Move action and select the original type, provided the configuration still supports it. Review fields and workflow behavior carefully when reversing the change.
Conclusion
To change an issue type in Jira, open the issue, select Move, choose the destination type, map required fields, confirm the action, and verify the result.
The main risk is assuming the change only updates a label. Issue types can affect workflows, fields, automation, boards, permissions, and reporting.
Start with one issue, check the project configuration, and test the new behavior. When your team needs a different approach to structured work management, evaluate platforms such as ONES.com alongside your existing process.
That approach removes the uncertainty around issue corrections and helps you keep Jira work accurate, visible, and useful.
Meta Title: Jira Change Issue Type: Step-by-Step Guide
Meta Description: Learn how to change a Jira issue type safely, review permissions, handle bulk changes, avoid workflow problems, and verify every update.
