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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,007
Community Members
 
Community Events
184
Community Groups

Automate task duplication from one project to another upon status assignment to done

I would like to transfer issues from one Jira Work Management Project to another upon completion of the workflow for the 1st project. 
So in our example, when the status reaches status of done in the first workflow project and the 2nd team is ready to pick it up I would like to create an automation that copies it over to the next Project which is also is also a JIra work management project.

How do I create that automation?

2 answers

1 accepted

1 vote
Answer accepted
habib rahman
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.
Mar 20, 2023

Hi @Aryeh Schwob my name is Habib I will try my best to help with this request: 


In Jira Work Management, you can create an automation rule to transfer issues from one project to another upon completion of a workflow. Here are the steps to do this:

1. Start by navigating to the admin area of your Jira instance, and selecting "Automation" from the sidebar menu.
2. Click the "Create a rule" button, which will start the rule creation process.
3. Give your rule an appropriate name, such as "Transfer issues from Project A to Project B."
4. Under the "Triggers" section, select "When an issue's status changes," and then select the status that indicates completion of the workflow in Project A.
5. Under the "Actions" section, select "Create an issue in project," and then select Project B from the dropdown list.
6. Set the fields for the new issue, including issue type, summary, description, and any other fields that are relevant to the new project.
7. Map any custom fields from Project A to the fields in Project B.
8. Click "Create" to complete the automation rule.


It's important to note that this automation rule will create a new copy of the completed issue in Project B, rather than moving the original issue. If you want to move the original issue, you will need to use a different approach, such as manually moving the issue after it has been completed.


In summary, you can create a Jira Work Management automation rule to transfer issues from one project to another upon completion of a workflow. By following the steps above and setting the appropriate triggers and actions, you can create a streamlined process for moving issues between projects, allowing for a smoother handoff from one team to another.


If this helped please accept the answer as this could help others with the same issue as well. 
Thanks 

Habib. 

HI @habib rahman 

Thanks for your response.

I was able to create an automation to clone the issue as you suggested. The automation did work to clone the issue into the same project upon transition to the specified workflow status. However it failed when I tried to clone the issue to another project. Both projects are Jira Work Management. I checked the error logs for the automation and it says

"Clone Issue
Could not create issue in project/issue type

10058/10058
"

Do you know whats causing that?

habib rahman
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.
Mar 21, 2023

HI @Aryeh Schwob 


Based on the error message, it seems there might be an issue with the project permissions. Please check the following settings:

  1. Make sure that the user who created the automation has the necessary permissions to create an issue in the target project.
  2. Ensure that the target project has the same issue type as the source project.
  3. Verify that the target project is active and not in a read-only state.

If the above settings seem to be correct, you can also try the following steps:
  1. Check if there are any custom fields or required fields in the source project. You may need to create the same custom fields or required fields in the target project.
  2. Confirm that the workflows used in both the source and target projects are the same.

If the issue still persists, you can try cloning an issue manually to see if it is an automation-specific issue. This can help confirm whether the problem is with your Jira instance, network, or source and target projects.

Thanks 

Habib. 

Like Aryeh Schwob likes this

Hey @habib rahman 
I checked for the following issues:

  1. User is me. I am admin and team member in both projects. Automation is executed by me.
  2. Target and source project both are tasks
  3. I am able to add and remove issues to both projects, so they are both active projects
  4. There are no required fields in any projects
  5. Workflows are the same structure in both projects. (The steps in the workflow are named differently and there may be more steps in one project than in the other project) Both projects start with a beginning and end with done status (They have different names assigned to the status' though)
  6. I have tried cloning within the project to the same project and it was successful, it is only when I try to clone to another project that it fails.
Like habib rahman likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events