You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi
I have "Project A" and "Project B" in the Jira software and would like to set automation rule for "If I change the status of that issue in Project A, it must also change in Project B."
Example: In "Project A" the issue is in Close State and I change it into Close it should automatically change to same state in "Project B" into Close
What I do now is create one issue in "Project A" and directly move the cloned issue to "Project B" as different issue type(from Story to Task)
The issue show in "Project A"
The issue show in "Project B"
Currently the automation rule is set up as below but not able to work yet, not sure if this related to I have two different workflow in two projects...
Hi @SU YU SIOU ,
Your automation is correct but you need to create a global automation to do this.
1. Go to Jira Settings -> System
2. Select Global Automation
3. Create the rule
4. Change the scope in rule details
5. Add the projects that you want to perform this rule
Cheers!
Hi
Thank you for the instruction, it is still not work if two projects using different workflow.
Example: In "Project A" the issue is in Close State and I change it into Close it should automatically change to same state in "Project B" into "Done".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @SU YU SIOU
If you're looking for easily synchronize status between two cloned issues, I suggest you to try our Copy & Sync application.
You can map the workflows of two cloned issues so, in your case, when the source issue in Project A changes its status to Close, the target issue in the Project B will change to Close as well.
It seems that your needs for cloning and synchronizing between two projects go beyond the status synchronization. Feel free to take a look at our documentation to discover how it can help you manage more easily your processes.
You can also trigger recipes with Automation thanks to our API.
Don't hesitate if you have any questions, I'll be glad to help!
Regards
Thibaut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.