Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I capture the original project when I move an issue to a new project?

Peter McGrath
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 17, 2019

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? 

5 answers

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
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.
September 17, 2019

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.

1 vote
Antoine Berry
Community Champion
September 17, 2019

Hi,

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.

Antoine

0 votes
Joe Pitt
Community Champion
September 17, 2019

How are you searching for the issue? I presume you have at least browse permission in both projects. When you move an issue you can still find it if you search for the original issue number. If you aren't searching for the original number try that. 

0 votes
Jack Brickey
Community Champion
September 17, 2019

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.

0 votes
Mohamed Benziane
Community Champion
September 17, 2019

Hi,

you can clone the ticket instead of moving it.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events