I want to create automation that any stories, tasks or sub-tasks inherit the component from the epic when a new issue is created. I created the automation below but when testing it states no actions performed and the component from the parent epic was not added to the task.
The branch you are using is assuming the trigger issue is an epic. That does not seem to be what you want, correct?
Instead you want a rule which can handle the different issue types. Perhaps more like this:
You may be able to collapse this rule down to always copy from parent (for all issue types). I recommend getting something to work first and then experimenting to improve the rule.
Kind regards,
Bill
Good Morning @Bill Sheboy
I like where this was going, unfortunately epic link was not available, but i was able to use related issue condition. Thank you so much for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Bill Sheboy This worked like a charm! I had a different use-case but some bits of this solution worked for my use-case. Thanks for your inputs!
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.
I updated the question. The audit log shows that no action was performed and it states branch rule/related issues. No related issues that have been updated since the last time this rule executed could be found. I have "only include issues that have changed since the last time this rule executed" checked
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.