Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)

You can move a Jira issue across projects using native move semantics to preserve comments, attachments, worklogs, and audit data. This approach rekeys the issue ID without relying on clone-and-delete methods.

Using Jira's native issue move semantics is the best way to move issues without clone and delete. It preserves historical audit data, comments, and worklogs while rekeying the issue to the new project.

Yes, moving a Jira issue to a different project using native semantics preserves worklogs, attachments, comments, and historical audit data. The issue key is rekeyed to match the target project configuration.

You need to specify an issue type when moving Jira issues to a project with a different type configuration. Use the --issue-type parameter to ensure compatible workflow and custom field values in the destination.

Moving Jira issues to a new project can drop incompatible custom-field values and reassign the workflow. A risk-aware confirmation step ensures you understand these potential data losses before executing the move.