Jira Automation: Populate Due date with Release Date of Fix Version containing "202"

[Stewart_ Emily _ Global D_T]

Background: A particular group of teams use fix versions for PIs and monthly releases. PI fix versions contain "PI" and monthly releases contain "202" as in 2026, 2027, etc. A work item could have multiple PI fix versions and a monthly release fix version on it.

Requirement: Configure automation to populate the Due date field with the release date from the monthly release fix version, which is a fix version name that contains "202"

What I've tried:

Condition: If a work item matches JQL: fixversion ~ "202*" (This is working correctly.)

Action: Edit work item field: Due date 

1) {{issue.fixVersions.releaseDate.max.jiraDate}} -- This works, but if the PI fix version's release date is later than the monthly release fix version, then this doesn't populate the right date.

2) {{issue.fixVersions.name.match("(?i).*202*").last.releaseDate.jiraDate}} -- This doesn't work. I've tried first in place of last, no first or last, and no .jiraDate. The value doesn't appear in the audit log or populate the Due date field.

{{issue.fixVersions.filter(v -> v.name.contains("202")).last.releaseDate.jiraDate}} -- This doesn't work. I've tried first in place of last, no first or last, and no .jiraDate. The value doesn't appear in the audit log or populate the Due date field.

[Gor Greyan · Accepted solution]

Hi @Stewart_ Emily _ Global D_T

Welcome to the Atlassian Community!

I agree with Gabriela’s approach here. The important part is to keep each Fix Version object in context while checking the name.

I would also suggest adding a temporary Log action first.

{{#issue.fixVersions}}
Name: {{name}} | Release date: {{releaseDate}}
{{/}}

This will confirm whether Automation can see the release date for the version containing 202. Once the log shows the expected value, you can use Gabriela’s smart value in the Due date field.

[Stewart_ Emily _ Global D_T]

Thanks, Gor!

[Gabriela · Accepted solution]

Hi @stewart_Emily_Global D_T,

Two things are sinking your attempts. filter(v -> …) is Jira-expressions syntax, not automation smart values, so that line just renders empty; automation has no lambda filter. And .name.match(…) collapses the list to plain text, so there's no version object left to read .releaseDate from.

Keep each version in context and test its name inside a loop instead:

{{#issue.fixVersions}}{{#if(name.contains("202"))}}{{releaseDate.jiraDate}}{{/}}{{/}}

That walks every fix version and outputs the release date only for the monthly one whose name contains 202, so a PI version's later date never wins. It assumes one 202 version per item, as you described; two would concatenate. The loop plus {{#if}} filter pattern is documented in Automation smart values – lists.

Best, Gabriela

[Stewart_ Emily _ Global D_T]

Thank you, Gabriela!