nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automatically block parent ticket if child is blocked

motherg

Hi all,

I was wondering if there was anyway to automatically block a parent ticket (epic in this case) if a child ticket is blocked? Specifically, if a child ticket has a link of "blocks/blocked by" (as opposed to adding a flag), can the parent Epic automatically have a link added to the other Epic that the other child ticket belongs to? These different epics and stories would be in different projects.

I feel some sort of better example might be needed as it's gnarly to explain:

Given Child A belongs to Parent A (in Project 1)

AND Child B belongs to Parent B (in Project 2)

When I add a link that states Child A blocks Child B

Then Parent A automatically gets a link to say there's a blocker in Parent B

What do you reckon? The reason for this is that in the Plans/Advanced Roadmap, if you're looking at a higher flight level where you only need to go down as far as an Epic, you can't see the fact that some of the children are blocked, so you have a misleading picture.

Accepted answers

Bill Sheboy

Hi @motherg

First thing, well done in your clear explanation of the scenario!

I believe that would be possible using an automation rule, triggered on the issue linking, and using conditions and branching to update the correct epics.

This rule would need to be multiple-project or global in scope as it is modifying multiple projects. Such rules are managed by Jira site admins, so please talk to your admin for help.

I suggest trying to create the rule, and if you run into challenges, post images of your rule and explain what is not working as expected so the community can help. To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

All comments

Bill Sheboy

Hi @motherg

First thing, well done in your clear explanation of the scenario!

I believe that would be possible using an automation rule, triggered on the issue linking, and using conditions and branching to update the correct epics.

This rule would need to be multiple-project or global in scope as it is modifying multiple projects. Such rules are managed by Jira site admins, so please talk to your admin for help.

Kind regards,
Bill

motherg

Thanks Bill, it's good to hear that you think it might be possible. I'll have a dig in to it and see where I get to (and report back). Fortunately I am an admin so I should be able to do a lot of it myself.

motherg

@Bill Sheboy we haven't managed to get this to work unfortunately, there doesn't seem to be a way to trigger the parents to link based in the act of a child being linked.

Bill Sheboy

I think you can still use the Issue Linked trigger for that one. For your scenario(s), the key is which issues are checked / branched to.

If you post images of your current rule and audit log details, that will provide content to make adjustments. Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud