How to store the old issue key when an issue is moved from one project to another

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

While moving an issue from one project to another the issue key gets changed. But this issue key can't be found anywhere unless you go to the history of the ticket and look for the key change. This article will show you how to keep track of the original issue key of a Jira issue using an Automation rule when you move it to another project.

Solution

  1. Create a new custom field called "Old Issue Key" of type single line text

  2. Add it to the issue screen in the destination project

  3. Setup an automation rule with the below specification a. Issue Moved trigger and configure source and destination projects if needed b. Add the 'Edit Issue' component to set the value for the "Old Issue Key" field. c. Use the below smart value in the "Old Issue Key" box {{changelog.key.fromString}}

NOTE

Using this rule, you can only store the issue key of the previous project. So, if you move an issue to different projects more than once, the field only holds the issue key from the project where it was last moved.

Updated on July 14, 2024

Still need help?

The Atlassian Community is here for you.