Hi
The requirement is simple, if epic has a label then that label is also should be added to child issues.
I have other automation too
Whenever epic label is updated copy the label values to child issues .
And whenever new issue is created and issue type is not epic then copy the labels of epic to child issues.
But our customer need one more automation to schedule daily to perform same action if any issues which may have missed from above two automations.
For that
Trigger : i am using Scheduled
JQL : issuetype = epic AND labels in (a,b,c,d,e)
Branch
Story( or Other Work Items in Epic)
Using smart values conditions
Tried {{triggerIssue.labels.toString}} contains a etc...
failed
Tried {{issue.parent.labels.toString}} contains a etc..
failed
Tried {{branch.parent.labels.toString}}contains a etc..
Failed
Help me with smart value to check epic label in branch , the above all checking child issue labels hence it is failing.
Action :
add label a etc.
This is how my whole automation.
Thank you!
Sagar
Hi Everyone,
I found a fix,
Before branch i created a variable
Variable Name : Epiclabellist
Smart value : {{issue.labels}}
And in branch
Smart condition i written has
{{Epiclabellist}} contains a
It worked!
Hope this may help to anyone
Hi @Venkata Sagar Ganesh Rao Mahendrakar ,
I guess you can just use the then action "Copy Label from Parent work item" every time the epic is updated (as the trigger).
Best
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan, Thanks for the response!
But i need like when a label is found in Epic then only that a label should add in the child issues.
We can use but in Epic there may be x,s,a, and more labels but i don't need all of them i only need a.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Venkata Sagar Ganesh Rao Mahendrakar
I read in your post you have a solution for some of the possible cases to copy the labels. Please consider there are additional ones...including for the scheduled rule scenario. Please see this article I wrote on synching / summing fields between parent and child work items to learn more about those cases:
Kind regards,
Bill
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.