I have a little bit difficult requirement. I have an epic and I will manually link this epic with an issue „XYZ“. My epic is linked with child issues. I would like to automatically link my issue „XYZ“ with all child issues of the epic. Is it possible with automation rules? Or does anyone has another idea?
I have an issue „ABC“ that is linked with other issues over the issue link type „relates“. Now I create another issue „XYZ“ and link it with my issue „ABC“ with the link type „fulfills“. I would now like to automatically link my new issue „XYZ“ with all linked issues of issue „ABC“ that are linked with issue „ABC“ over the link type „relates“. Does anyone has an idea for that?
Both of your scenarios sound possible to implement with automation rules. The part I do not understand is how you are identifying the "target" item to link. Would you please clarify your question?
So the question: is XYZ-123 hard-coded, a field in the Epic, or what?
The first two cases can be handled with automation, the what unknown case is, well...undefined.
If you flip the trigger, and start from XYZ-123, I don't see how you would find the Epic unless it was already associated to the issue.
That sounds possible, and I recommend first writing down some example cases of the linking to help you create rules.
And here are some example rules in the library to give you ideas:
Once you create your rule, if you run into problems please your rule back here so the community can give you ideas. Thanks!
Of note: as this rule spans different projects, it will need to be a global-level rather than a project-level rule. This means you need to monitor the execution usage limits. Please see here for more details:
[Jira Software - Cloud all with Next Gen projects]
I have an automation that, based on an issue type, creates issues on other kanban boards. For example, when someone creates a PROJECTS issue of issue type Bare Metal, an automation runs, resulting in three new issues on different kanban boards being created (i.e., EMON-3, ENET-14, & DCT-72). Of course, these newly created issues are linked to the PROJECTS issue (i.e., PROJECTS-1) linked as...
PROJECTS-1 is linked to
I'd like an automation that will link the children issues to each other. Thus,
Any ideas on how to make this happen? I assume doing this in the same automation that creates the linked issues (i.e., EMON-3, ENET-14, & DCT-72) is the best place to do it, but maybe it's a separate automation that runs when each of these issues are themselves created?
Hi @Paul Benati
Your question seems related to, and different from, Robin's question. I recommend creating a new question in the future to help the community find it faster. Thanks!
The challenge with your use case is it probably needs nested branches to iterate over the created issues to do it in one rule, and that is not possible with the current automation capabilities.
Instead you may want to:
Hi @Paul Benati
I don't that structure will work because Link Issues is expecting on key, not a list.
You will probably want to change your branch to use JQL that satisfies all of your criteria, and then link.
I don't see a viable path as I'm starting from the child, as per your earlier recommendation. Thus, I have to first branch to the Parent to find its linked issues. Once I find them, I can't iterate on the looked-up issues and branch over them since nested branches aren't supported.
Do you have any other thoughts on how to solve this?
If we go back to your originally posted issue structure, this is a fairly specific use case for automation. I believe you can do this with 4 global (multi-project) scope rules. This assumes you always add the 3 issues. (So, change the rules if that assumption changes.)
First rule in PROJECT:
Sibling rules (one in each project: EMON, ENET, and DCT). Each of these rules should enable the option Allow rule trigger in the details. This allows the first rule to fire the sibling rule.
What do you think?
Okay, I figured it out. No branching required!
[Note: for testing purposes, I used a manual trigger.]
Steps (check out the attached for details)
Please note, the reason I switched the sibling rules (EMON, ENET, DCT) to use a rule trigger other than Created Issue is there is no guarantee that all three issues will exist by the time you want to link to them. So your second lookup issues call may find 0-3 issues, subject to the timing of rule execution/trigger capture in the Cloud.
Any thoughts on how to prevent the same sibling from linking multiple times? I'm doing a check prior to linking to see if the sibling is already linked, but I believe the asynchronous nature of the executions is tripping this effort up.
What if I added a re-fetch command after each "Link issue to" command as shown in the last image?
Note: the two automatons below are triggered by Comments. The second image shows the comment payload for the 2nd automation.
With the potential for parallel rule execution you will not be able to solve the timing issue with the re-fetch in this case. For example, the re-fetch might occur just a moment before it is needed to solve the duplication problem.
Four potential approaches to "solve" this are:
Excellent insight, thanks. I chose to pause and re-think the problem. There are two goals:
This led me to add the sibling links into the Description of the parent and its children. And then the distribution of comments was a quick regex parsing of the Description.
Thanks again for all your help Bill!
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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