nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to get old Jira issue key based on the new Key value

Gopinath Velayudhan

Hi -

I have a situation where I want to find the old key of the ticket that have been moved to a new project. For example

tiket AAA-123 was moved to BBB-456. I have BBB-456 and how do I get the old key value. Is there any query GUI or Database that i can use to get this information out. I have about 500 tickets so I eally do not want to go to the history tab to find the old key value.

any help is very much appreciated.

Accepted answers

Jobin Kuruvilla [Adaptavist]

You can find it from the "ChangeItem" table in JIRA. Look for rows where the field name is "Key".

All comments

Jobin Kuruvilla [Adaptavist]

You can find it from the "ChangeItem" table in JIRA. Look for rows where the field name is "Key".

Henning Tietgens

You can create a scripted field. See here: https://answers.atlassian.com/questions/148169/display-previous-key-of-moved-issue

Matt Doar_tzgiej

In 7.2 it's not in the history tab of an issue, so I'm not sure it is recorded in ChangeItem. The old project keys are recorded in the project_key database table though

sanjay mishra_g6pn8y

You can use Curl to get the New Key value

ex: old key ABC-123 is moved to new key XYZ-123

curl -D- -u user:password -X GET -H "Content-Type: application/json" https://url.com/rest/api/2/issue/ABC-123

command will give the new key here is sample response

HTTP/1.1 200
Cache-Control: private
Expires: Wed, 31 Dec 1969 19:00:00 EST
X-AREQUESTID: 719x18566421x5
X-ASEN: SEN-2060384
Set-Cookie: JSESSIONID=97D7E069C110FDE95E3A7CD6BE3A4B80;path=/;Secure;HttpOnly
X-Seraph-LoginReason: OK
Set-Cookie: atlassian.xsrf.token=BEJ7-XRGE-Y44Y-ZOG4|9e2281670790ee533bc67671f88518a8c4ca28f5|lin;path=/;Secure
X-ASESSIONID: we53k
X-AUSERNAME: user
Cache-Control: no-cache, no-store, no-transform
X-Content-Type-Options: nosniff
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Date: Mon, 15 Apr 2019 15:59:02 GMT

{"expand":"renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations","id":"960187","self":"https://url.com/rest/api/2/issue/960187","key":"XYZ-123","fields":

Victor Peters

I've used the REST API to extract issue information, but of all issue information retrieved by the REST API, the previous issue key of a moved (to another project, during which process the issue key has changed) was not among the information supplied bij de REST API call.