Migrating issues between two projects in the same Jira cloud instance

[János Hinkel]

Hello Community!

I did find questions and answers to this topic but haven't found a fresh topic on this, so this is why I'm asking.

Our client asked us to move issues from an existing project to a new one while keeping the issue ID's.

My questions would be:

- Issue ID's and Issue Keys are not the same in the background, right?

- If the issue key changes from AAA-123 to BBB-456, will the ID remain the same in the new project?

- Can it be confirmed that all the connected development data (commits etc) will be linked and will work from the new project as well?

- Can an addon or app assist us in this task?

Thank you very much for your answers!

Cheers

János

[Viðar Svansson]

Not sure about Planview but with Tempo you can track hours worked on projects or other types, such as version, component, team, and user.

[Rob Davis]

Thanks @pjesi but... "In my organisation we use the timesheets in Planview" and " I wondered if there was an automation such that activity of each user in JIRA (and other Atlassian products) could be used in an automation to populate the PlanView timesheets." We are not using Tempo (at the moment), but it looks worth investigating. But we have to use PlanView, so I was looking for a solution that worked with that, as stated already.

[Basil Jose]

Hi Rob,

We are in the same situation as well. Did you find a solution for this?

[Melva Peed]

Hello -  We too use Planview for time tracking and will be moving to Tempo.  I need tempo timesheet to populate Planview.  Any updates on this?