this is probably really simple but its driving me mad!
I have a Sub Task that i need to use as a trigger to create another sub task that sits under a different task but i cant get the automation logic right to "find" the other task.
any help would be really appreciated
Thanks for the welcome,
That's where i am having the trouble, i cant work out the logic to "find" Task 2, which seems so simple.
I am using the Summary with a condition where it contains "- Testing" as the identifier for Task 2 but like i say, i cant work out how to build the rule that states when an issue moves from in progress to done, if "- Testing" and then create the subtask
have only been working with the automation for a week or so any tips would be really handy?
Ok, in the automations, you've got four types of block you can use - triggers, branches, actions and conditions. I think you should be making use of a condition that looks at the summary field, either with JQL to see if it matches, or directly with a "contains" type statement.
So my understanding to the Epic Parent is that it will find the Epic Parent of the current issue.
My thinking was that as the Subtask "- Design Solution" has been transitioned to Done the rule would look for the Epic and then look for a Summary called "-Testing" and create a sub task.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
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