My organization is using Jira Cloud. Users routinely create issues in a central "Triage" project. Tickets are then moved from that project to other projects for implementation.
We would like to be able to track metrics on tickets that originate in this triage project, but when the tickets move, we can't seem to access the originating project or issuekey. Ideas?
Moving issues between projects is generally not a good process to do - it's intended for tidying, archiving and when people put things in the wrong place by mistake. So it can be a lot of work, and you lose information in front of the users (it's still there, but not directly, only in the history)
Annoyingly, the "was" operator does not support "project", so we can't use JQL to get it.
On server, I'd write a scripted field to fish it out of the history and display it directly, but I am not sure you can write an equivalent for Cloud (I'd take a look at the scripting and automation apps in the marketplace)
The only thing I can think of that doesn't require coding of some form is to clone the issues out of the project instead of moving, then close the original, but that leaves you with piles of dead, duplicated issues.
I would create a custom field (checkbox probably) and add a custom configuration for that project that has default value ticked. You do not have to display it and can use it in JQL so you can easily retrieve all the tickets that were created in that project.
here is a thread you might wish to read - How-to-find-issues-that-were-moved-from-one-project-to-another
ultimately I think you will want to use an addon along with a text based custom field to capture the current issue key when moving.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events