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

Help with how to use Jira Automation to find distinct sprints for an Epic's children

Marc Schadee

Hi!

I could use some help with finding all sprints that work for an epics children

I use this lookup "Epic Link" = {{triggerIssue.key}} AND Sprint is not empty

{then i create a variable {lookupIssues.sprint.name.distinct}}

When i print to the audit log i get this

RPT-2024_Sprint08, RPT-2024_Sprint09, RPT-2024_Sprint10, RPT-2024_Sprint08, RPT-2024_Sprint09, RPT-2024_Sprint10, RPT-2024_Sprint11, PM1 Backlog, RPT-2024_Sprint10, RPT-2024_Sprint11, RPT-2024_Sprint11, RPT-2024_Sprint08, RPT-2024_Sprint07, RPT-2024_Sprint08

which is great except for the duplicates (work items that were in 2 sprints)

So the issue is I am trying to parse this list (or use substring) to find just unique sprints but nothing im doing is working so far.

My current idea was to use substring but that seems to not work with the list and returns [] [] [] []

Any suggestions on how to parse this list? my Thought was to use a character count as there is a standard naming length that does not change but open to help

Accepted answers

Marc Schadee

so took some thought but for anyone trying to parse unique sprints that an epic has work that has been this is a way

lookup -> "Epic Link" = {{triggerIssue.key}} AND Sprint is not empty

create variable (smart value) {{#lookupIssues}}{{#sprint}}{{#if(not(equals(state,"future")))}}{{name}},{{/}}{{/}}{{/}}

(I only wanted current/closed sprints youll need to play with above if you want different)

create variable (smart value) {{firstvariablename.split(",").distinct}}

All comments

Marc Schadee

so took some thought but for anyone trying to parse unique sprints that an epic has work that has been this is a way

lookup -> "Epic Link" = {{triggerIssue.key}} AND Sprint is not empty

create variable (smart value) {{#lookupIssues}}{{#sprint}}{{#if(not(equals(state,"future")))}}{{name}},{{/}}{{/}}{{/}}

(I only wanted current/closed sprints youll need to play with above if you want different)

create variable (smart value) {{firstvariablename.split(",").distinct}}

Bill Sheboy

Hi @Marc Schadee

I am glad to learn you found the workaround, and...

FYI, the distinct was working as expected: it just did not match your scenario because the sprint field can contain multiple values, and "distinct" was over the sets of values in this case.

For example, if the issues had these sprint values:

issue A: sprint 1, sprint 2, sprint 3
issue B: sprint 2
issue C: sprint 4
issue sprint 2

Then using this:

Would produce the following, with a list of arrays, and not necessarily in this ordering:

[sprint 1, sprint 2, sprint 3], [sprint 2], [sprint 4]

The list of sprints for issue A is distinct as a set, even though it contained overlapping sprints with other issues.

As you found, the workaround is to expand everything into a variable so it can be reprocessed as a list for using distinct later. One gotcha for this technique is ensuring the delimiters are consistent, helping split() to work predictably later. The fix for that is often to replace(", ", ",") before the split attempt.

Kind regards,
Bill

Marc Schadee

Hey @Bill Sheboy !

I missed mentioning a step! in the first variable i add commas (bolded below) deliberately to have a comma between each sprint iteration since you can get multiple sprints as 1 value but they are always separated as a comma (that im aware),

e.x.

[Sprint 1],[Sprint 1, Sprint 2],[Sprint 2]

{{#lookupIssues}}{{#sprint}}{{#if(not(equals(state,"future")))}}{{name}},{{/}}{{/}}{{/}}

to get (because its now a string we lose the [])

Sprint 1,Sprint 1,Sprint 2,Sprint 2

then run {{firstvariablename.split(",").distinct}}

Sprint 1, Sprint 2

and thank you! Im pretty certain i got that last bit off of one of your prior comments!

Marc Schadee

Really the best part was getting this to work outside of a for each branch

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

automation