I am creating Automations to perform the following:
I would like for the process to be:
Thoughts on how to compare an automation to what is currently on a board? Thank you in advance!
Hi @Alisa Johnson ,
Would start looking into if there's any association between the playtest and smoktest ticket. Without some kind of pattern or association, it will be harder to automate and find the smoke test that went along with the playtest.
if the playtest is link to smoketest upon creation, then you setup an automation to see if there is a link ticket smoke test during the transition to complete. If not, create one. If yes, don't perform any action.
If I am reading your requirements correctly, you:
To clone and issue (you could also create an issue, if desired). See how the issues are linked in the "More options".
I am not sure the exact conditions you are looking for, but you can use an if/else block to check for already existing smoketests. If none exist, create a new ticket.
I hope this give you some ideas on how to start on some Automation rules. Please let us know what you think!
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events