SaltfishTry for free

How to Change Issue Type in Jira

·2 min read
In this article

Converting issues from one type to another is a common task in Jira project management. Whether you need to change a task to a story or convert a bug to an epic, understanding the process helps maintain proper workflow organization.

This tutorial walks you through the complete process of changing issue types in Jira, including handling cross-project moves and status updates that may be required during the conversion.

Here's how to change issue type in Jira

  1. Navigate to the Jira issue you want to modify from your project board.
  2. Locate and click the three dots menu icon in the top-right corner of the issue.
  3. Select the 'Move' option from the dropdown menu that appears.
  4. If working with a service project, transfer the issue to a different project that supports your desired issue type (such as a Scrum board).
  5. Select your preferred issue type from the available options (for example, choose 'Story').
  6. Click the 'Next' button to proceed to the status configuration step.
  7. Modify the status setting to specify where the converted issue should be placed in the workflow.
  8. Review your changes and click 'Confirm' to complete the issue type conversion.

Your turn to show how it works.

Build a walkthrough of your product with Saltfish, then share it with your customers.

Create a guide with Saltfish

Frequently Asked Questions

Yes, you can change issue types within the same project as long as both the current and target issue types are configured for that project. Service projects may have limited issue types, requiring you to move to a different project type like Scrum or Kanban.