It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

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 Leader Sep 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

Hi,

you can clone the ticket instead of moving it.

0 votes
Jack Community Leader Sep 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
Joe Pitt Community Leader Sep 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. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

365 views 1 3
Join discussion

Community Events

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

Events near you