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

Surfacing all Stories belonging to Sprints that contain specific text

Dominic Fosson

Background

We release major releases quarterly. Each of our Product teams works in 2-week sprints within each major release period and we're struggle to bring together all of the issues being worked on over the course of each sprint within each major release - in large part because each team names their sprints uniquely; however, each one contains the name/id of the sprint (e.g. 2024.3.1.0)

The Ask

As a potential solution, I'm trying out ScriptRunner in the hopes that it can provide the searching capabilities needed. As an example, I'm trying to surface all of the Stories that belong to a Sprint whose name contains "2024.1.1.0". This would work great as it would require no additional record-keeping from our teams and would provide a way for me to consistently stay ahead of these reports as I already know what the sprint ids will be.

I've played around with the JQL AI in ScriptRunner and haven't been able to make it work. Is something like this possible?

Accepted answers

Kalyan Sattaluri_iinm1n

Hello @Dominic Fosson

Two options:

Without Scriptrunner: (reference)

project in (KPMS, FNQD) and sprint = "22024.3.1.0"

With Scriptrunner: (reference)

issueFunction in issueFieldMatch("Project in (KPMS,FNQD)", "Sprint", "2024.3.1.0")

When projects KPMS/FNQD need to be replaced with your specific ones.

Please try and let us know.

All comments

Kalyan Sattaluri_iinm1n

Hello @Dominic Fosson

Two options:

Without Scriptrunner: (reference)

project in (KPMS, FNQD) and sprint = "22024.3.1.0"

With Scriptrunner: (reference)

issueFunction in issueFieldMatch("Project in (KPMS,FNQD)", "Sprint", "2024.3.1.0")

When projects KPMS/FNQD need to be replaced with your specific ones.

Please try and let us know.

Dominic Fosson

Thanks, Kalyan! I really appreciate you responding. I tried the following and it timed out due to "too many issues" (though I know there's only a handful):

issueFunction in issueFieldMatch("Project in (PD)", "Sprint", "2024.3.1.0")

I'm still learning here, but a couple follow-up questions I have are:

1. Given that I'm looking for the results to surface stories, shouldn't there be some callout in the JQL that references "stories" specifically?

2. I'm trying to work-around that the fact that sprints across our different product teams take on different naming structures (e.g. "Profile Re-design 2024.3.1.0" or "Admin Experience Catalog Work 2024.3.1.0"). They'll often start/end with different text, but they'll each contain the Sprint name ("2024.3.1.0") somewhere within them. Does the query you gave account for this "wildcard" element?

Kalyan Sattaluri_iinm1n

hello,

If you want only stories, append additional clause:

issuetype = Story and issueFunction in issueFieldMatch("Project in (PD)", "Sprint", "2024.3.1.0")

If above is timing out, try below as well,

issuetype = Story and project in (PD) and sprint = "22024.3.1.0"

Both above queries are looking at partial string in sprint name so should be good with your criteria.

Dominic Fosson

Thank you, Kalyan.

The first query was valid, but timed out (again, it should only return a small handful of issues).

The second was invalid because "The operator '=' is not supported by the 'sprint' field."

If the query itself seems like it should work, maybe I just need to veer my research into overcoming these timeout issues.

Dominic Fosson

Ah! I copied what you provided, but this time replaced "sprint" with the field's ID and that did the trick! Thank you very much for your help, Kalyan!

There was one additional piece I was looking to build upon by this that I haven't nailed down either - if you'd be willing to provide a bit more assistance.

This query has provided all the stories brilliantly. Now, I'm looking for a way to do the same, except to surface only the Initiatives of those Stories. Given that Initiatives aren't aren't themselves aligned with a Sprint, what would the query look like to surface just the initiatives that are the parents of Epics that are the parents of Stories that belong to a certain sprint?

This is the query that surfaced the Stories satisfactorily:

 issuetype = Story AND project in (PD) and cf[10007] in ("2024.1.1.0", "2024.0.0.0", "2024.0.1.0", "2024.0.2.0", "2024.0.3.0")

Dominic Fosson

Hannes Obweger - JXL for Jira

Hi @Dominic Fosson

if you're open to other solutions from the Atlassian Marketplace, this should be easy to do using the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. Using JXL's text filter option, you can build a view like e.g. this in just a couple of clicks:

For more sophisticated filter operations, you can also use regular expressions. I should also add that JXL can do much more than the above: From support for configurable issue hierarchies, to issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes

Dominic Fosson

This looks incredible - appreciate you reaching out. I'm going to check it out now.

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

jira-cloud

sprints

stories