I have created an automation rule to create an epic and child issues. That works.
I would like the rule to assign the epic being created as part of the automation to a parent.
I saw a similar post and tried the recommendation and it works somewhat.
This is a manually triggered rule. If I execute from an epic backlog, it does update the parent for an epic but it is the epic being viewed in the backlog--not the epic being created as part of the automation. I would like it to update the epic parent of the epic being created as part of the automation.
I was hoping someone could advise where the rule should be amended.
Hello @Kim Vencill
Welcome to the Atlassian community.
One way to solve this is to replace what you have here:
...with a branch to Most Recently Created Issue:
I notice though that you have another branch already - a Smart Value branch.
Branches can execute in parallel, so your branch to update the most recently created issue could be running at the same time as the other branch. Without knowing what you are doing in that other branch, it is possible that there may be unexpected results by adding the branch I suggested. What does that other branch do? What is the rest of the Automation Rule.
The other branch was to create the child stories under the newly created epic and that works. I made the change you suggested and it gives me the outcome I needed. Adding a screenshot in case anyone else would find this helpful if they land here with the same question.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.