Identifying Tickets that have moved between projects (Key Change)

wvacchiani January 9, 2025

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

3 answers

1 accepted

1 vote
Answer accepted
Anahit Sukiasyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2025

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 January 9, 2025

Hi Anahit,

Thanks.  That's the answer I was expecting.

Good to know.

Regards

Ward

 

Like Anahit Sukiasyan likes this
Anahit Sukiasyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 9, 2025

Happy to help!

Please accept the answer.

Have a nice day!

0 votes
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 10, 2025

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":

jira-excel-export-issues-selected-fields-with-repeating-change-history.png

That's pretty easy to do.

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

0 votes
Yuliia_Borivets__SaaSJet_
Atlassian Partner
January 9, 2025

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.

issues moved between projects.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events