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
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 all! Previously I made an automation that clones an issue (ISSUE-1) from project "A" to project "B" when the aforementioned issue is transitioned to a particular status. So I have:
Well, now I need to create another automation to transition that cloned issue (CLONE - ISSUE1) to another status when the ISSUE1 is transitioned. Both destination status have different names. I tried with the "Transition Issue" task but this is not useful for me.
Is this possible? How?
Hi @Nicolas Gomez and welcome to the community,
Could you please share a screenshot of your rule? I´m not quite sure if I can follow correctly especially when we talk about "transition" which is a main part of workflows and status.
As far as I understood correctly it´s about the name of the issue after the clone.
Please corret me if I´m wrong and if possible please provide some screenshots that describe your problem.
This is the first automation. Only in charge of cloning an linking the tickets
Now, I want to create another automation to "sync" the status between this cloned tickets (Different projects, transitions and statuses). For instance, if the cloned ticket is moved (transitioned) to the status X of that project, I want this action triggers a status change in the original ticket (To the status Y, remember that both projects have different structures)
The following rule is an example of what I guess your requirement is about.
In my case the previous rule cloned an issue from project JT to project CC and setting the issue link (like in your screenshot).
Whenever (in my case issue type bug) issue in project JT is transitioned from "selected to development" to "Done" the branch checks if there is a linked issue of type "clones" in the trigger issue. If so the transition for that linked issue will be done.
Hope this was helpful. Please let us know if you have any further questions.