Identifying Tickets that have moved between projects (Key Change)

[wvacchiani]

Hi,

Is there anyway in Jira, using JQL, of identifying tickets that have moved between projects, so that their key would have changed.

I found this reference from over 4 years ago:

Solved: Track the tickets moved from one project to other ...

This suggests scriptrunner or equivalent JQL extensions can do it, but I'm wondering if things have changed with JQL to provide the same capability.  I'm have my doubts but thought I would ask.

Any help will be appreciated.

Regards

Ward

[Anahit Sukiasyan · Accepted solution]

Hi @wvacchianiin standard Jira JQL, there is no built-in way to track tickets that have moved between projects I guess, as JQL does not support historical tracking of project changes or key changes natively. The workarounds can be ScriptRunner (or Similar Apps), Jira audit logs, Using Advanced Roadmaps or Reporting Tools or Jira REST API.

[wvacchiani]

Hi Anahit,

Thanks.  That's the answer I was expecting.

Good to know.

Regards

Ward

[Anahit Sukiasyan]

Happy to help!

Please accept the answer.

Have a nice day!

[Yuliia_Borivets__SaaSJet_]

Hi @wvacchiani 

Unfortunately, JQL still doesn't work for searching issues that moved between projects. If you are open to alternative solutions, you can check this case: 

How to track tasks that moved from Project A to Project B

Issue History for Jira (developed by my team) can help track project changes for issues.

[Petru Simion _Simitech Ltd__]

HI @wvacchiani , 

When issued are moved between projects the issue history for each issue is registering two changes. One is that of the project and the second is for the issue key.

While going through each issue and observing this change in history is possible, it can be time consumming and error prone.

If you are open to using apps you can use Issue History Dashboard for Jira an app released by our company.

You can filter by Project and in the Field Updated you can add either value Project, or Key, or both. 

The attached example uses both and the result shows that issue with actuall key AP-5 was transitioned, and how it's project and issue key values have changed from the initial value to the actual value.

You can export your search result for csv for further analysis.

Regards, 

Petru

[Aron Gombas _Midori_]

The CHANGED operator would be the JQL based solution for your use case, but as the documentation says "This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only."

Maybe if there was another field, supported by CHANGED, was also changed that you could search for that other field!

If not, you can easily export your issues to Excel with their version history, then in Excel filter to those rows where the "Changed field" value is "project":

That's pretty easy to do.

(Discl. the app suggested is developed and supported by our team. Free for 10 users!)