Change a Jira issue to another issue type using Jira's native move semantics with jirac

To change a Jira issue type without changing the issue key, you can use the jirac CLI to apply Jira's native move semantics. This preserves the original identifier like PROJ-123 while converting it to a different type such as Bug or Story within the same project.

When converting a Jira issue type, the target issue type screen may drop custom fields that are not configured for the new type. The jirac CLI includes an optional pre-check to verify field availability and help you avoid losing data during the type change.

The jirac CLI applies native move semantics for changing issue types within the same project. For cross-project moves where the issue type also changes, it points you to Jira's standard move operation rather than handling the project transfer directly.

You can convert a Jira Story to a Bug using the command line by running jirac with a natural language request like 'change PROJ-123 to a Bug'. The CLI extracts the issue key and target type, confirms your intent, and executes the type-change operation.

Changing Jira issue types with jirac applies to administrative workflows where users need to convert between common types like Bug, Story, Task, or Sub-task. You need appropriate Jira permissions to modify issues and access the jirac CLI environment.

Limitations of changing Jira issue types within the same project include potential custom field loss if the target type screen lacks the required configurations, and the operation is restricted to supported common types like Bug, Story, Task, or Sub-task without cross-project transfer.