Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Moving tickets from one project to another without losing it in the original project


We're setting up different projects for each team. Every ticket created will move through a workflow within its project being handed off to the next team, who will create a new ticket in their project and work on it. I wanted to know if there is a way to move tickets from one company-managed Jira project to another, without losing that ticket in the original project? In essence, a copy of the original ticket must be moved to the new project and it must adopt the new project's tag. 

Thanks in advance for any help!

2 answers

2 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 09, 2022

Welcome to the Atlassian Community!

An issue can only be in one project at a time.  If you move an issue to another project, it can't be in both projects at the same time.

You can clone an issue though, then move the new version to the other project.  The clone process links the two issues together as well, so you can see where the new one came from.

Bear in mind that if the two projects are configured differently, you may lose data on the issue you move.

@Nic Brough I am interested to move a ticket to another project as part of an Automation.  However, I note that "moving" an issue technically can't be done in an Automation

Instead, the original ticket is cloned directly to the project and the original ticket is deleted.

I was wondering if you had any advice regarding any unforeseen consequences to moving an issue using this workaround?


Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 30, 2023

Moving issues between projects is not something you should automate or have as a part of a regular process.

The short version of my opinion here is "stop".  Your process may well be fine, but you have not set up Jira to match it.  Clone, move and delete are all things you should be running away from.  If you're using them, you probably have a problem with your process as it is mapped on to Jira.

I would want to take another look at your processes and then talk to your Jira admin about how best to support them!

Like Garret Duffy likes this

We have multiple Product and multiple Development teams.  Each team has their own JIRA project but Product teams share the same workflow status definition and Development teams have their own workflow status definition. 

Issues are advanced along a Product team's workflow until the final workflow stage.  Development team then reviews those "final stage" issues, toggles a custom field to "Ready" and then someone manually moves those toggled issues, to one of the Development teams' projects (destination project).  In the destination development project, one or more tasks are generated for the moved issues and those tasks are then advanced along the Development team's workflow.

I am enquiring about the underlined text above and how to make more efficient.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 01, 2023

It's the same answer, stop moving issues between projects, it's not the way to work in Jira.

You need to do one of:

  • Change your processes such that people create issues in the right project to begin with
  • Merge the projects so that people don't need to have to work out which project is right
    • (Both of the above would mean merging your workflows - the product team would own the first few status, the development the later ones)
  • Automate the product team's workflow so that when they move an issue to ready (I'd strongly recommend doing this with status rather than with a custom field), it creates a linked copy in the relevant development project.  Then automate the development project so that when a linked issue from product is moved to "done" by the developers, have it move the product issue to "development done"

The third option looks good for us and is close to what we're doing already.  The final automation step you describe looks very useful and I will try to make that happen.  

Thanks so much.

0 votes
Marlene Kegel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Aug 10, 2022

Welcome to the community, @Madhu.Rathnasekar.

I am Marlene from codefortynine.

With our Jira cloud app Deep Clone for Jira, you can clone and move tickets between all project types.

  • Simply select the issue you want to clone
  • Define the target project and issue type
  • Configure which fields you want to clone

If you clone on a regular basis, you can create presets for recurring cloning actions.

If you want to clone several issues at once, you can use the Bulk Clone feature.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events