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

ScriptRunner enhanced search - advanced blockers search

Esther Strom

We're looking for a way to easily view blockers and blocked issues in our boards. I was able to set up two saved filters using enhanced search, one using "blocks" and one using "blocked by":

issueFunction in linkedIssuesOf("project = DE", "blocks")

issueFunction in linkedIssuesOf("project = DE", "is blocked by")

The problem I'm running into is this: I get back the correct list of issues that are blocked by others, but when I open one of them, I can see that although the link is still in place, the issue that's marked as the blocker is closed (resolved), so technically it's no longer a blocker.

I'd love to just tell our users that they need to be responsible for updating links, but with the volume of issues we track, that's not feasible.

Is there any way to update the query to only return issues whose "blocked by" tickets are unresolved?

We are on Cloud; I know that there are some differences in ScriptRunner, so please keep that in mind when providing an answer.

Accepted answers

PD Sheehan

Yeah, like this:

issueFunction in linkedIssuesOf("projects = DE and resolution is empty", "blocks")

All comments

PD Sheehan

Yeah, like this:

issueFunction in linkedIssuesOf("projects = DE and resolution is empty", "blocks")

Esther Strom

Thanks. I didn't realize I could use more complex JQL than just the project name in the linkedIssuesOf params.

Esther Strom

OK, I marked this as accepted, and it seemed to work for one project's set of searches. I just tried to create a new set for a different project, though, and it's not quite working correctly.

I would expect that using status != Closed in the search would return only issues where the status isn't Closed (we can't use Resolution, as Closed is not our final status, so the resolution is not set at that point.) That clearly isn't the case, though, as you can see from this screenshot.

Is there anything obvious I'm doing wrong here, or is it a bug in the plugin? Or is resolution really the only bit of JQL that can be used in linkedIssuesOf?

PD Sheehan

This inner query applies only to the linked issues.

This says "give me all issues that are linked to open issues in the PHTP projects with the "blocks" link type.

If you want to exclude non-closed issues in the final list, you need to add a "and status != closed" outside of the issue query.

so perhaps:

status !=closed and issueFunction in linkedIssuesOf("project = PHTP and status != closed", "blocks")

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

cloud

adaptavist

jira-cloud