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; } } }

Delete link of an issue if the linked "blocked by" issues are in the status done with automation

Thies Uhlenbruch

We have several issues in our jira project which have dependencies and I want to automate the behavior of the dependencies under certain conditions.

For example we have a scenario like this:

1. PUT-1 is blocked by PUT-48 (Open)

2. PUT-2 is blocked by PUT-105 (Open), PUT-105 (Done), PUT-8 (Done)

3. PUT-34 is blocked by PUT-34 (Done), PUT-16 (Done)

... and so on ...

My goal is to check on a daily bases (scheduled) if the blocked by issues (1 to n) are all Done. In that case delete the link to all of them.

So how would I do this with jira automation because I guess that I have to use the lookup action with a branch.

Would be great to hear from you.

Thanks

Thies

Accepted answers

Trudy P Claspill

Hello @Thies Uhlenbruch

You could use a Schedule trigger to run the rule.

However you need to provide or get the list of blocked issues that you will want to check.

With a Schedule trigger you can include a JQL to select the issues you want to operate on.

Unfortunately Jira doesn't have a native "hasLinksOfLinkType" function. Because of that there is not a dynamic method to get just the issues that have "is blocked by" links to other issues. You will have to either provide an explicit list of issues to check, or use a more generic JQL to retrieve issues to check (i.e. project=X and issueType in (A, B, C)

The next component in the rule would be actually be a Condition for Related Issues rather than a Lookup Action.

Screen Shot 2023-04-12 at 11.23.02 AM.png

This condition will check that all issues linked to the primary issue (retrieved by the schedule trigger) with the "is blocked by" link are in a Done status. If they are, then the next step will execute. If they are not, or if there are no linked issues with that link type, then the next step will not execute and the rule will iterate to the next issue in the list retrieved by the schedule trigger.

The next step would be a Delete Links action to delete the l"is blocked by" issue links.

Screen Shot 2023-04-12 at 11.26.41 AM.png

All comments

Trudy P Claspill

Hello @Thies Uhlenbruch

You could use a Schedule trigger to run the rule.

However you need to provide or get the list of blocked issues that you will want to check.

With a Schedule trigger you can include a JQL to select the issues you want to operate on.

The next component in the rule would be actually be a Condition for Related Issues rather than a Lookup Action.

Screen Shot 2023-04-12 at 11.23.02 AM.png

The next step would be a Delete Links action to delete the l"is blocked by" issue links.

Screen Shot 2023-04-12 at 11.26.41 AM.png

Kelly Arrey

Hi @Trudy P Claspill would `issueLinkType = "is blocked by"` work in this context?

Here's the doc: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields/#Issue-link-type

Trudy P Claspill

You're right @Kelly Arrey ! I thought there was something like that but was looking in the functions reference instead of the fields reference. Good catch! That would indeed work in the schedule trigger for selecting the issues to run the rule against.

Kelly Arrey

I know what you mean @Trudy P Claspill, I wish all that documentation was on a single page so you could search it once instead of having to search each page individually.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

link

automation

dependency