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

JIRA Automation - Newly created child issue to have parents most recent Fix Version added

Christopher Vickery

Hi all,

I'm attempting to create an automation rule where a newly created child issue (e.g. story) will automatically take the parents (e.g. Epic) most recent Fix Version.

For example, an Epic contains 4 fix versions - CSP-24.1, CSP-24.2, CSP-24.3, CSP-24.4. The most recent fix version in the list of 4 is the last one added - CSP-24.4.

When a child issue is added to the Epic, preferably it shouldn't pick up all 4 (which is the automation I have in place at the moment). The child issue should only pick up the CSP-24.4 fix version as it's the most recently added in the group. This should only apply to child issues that are not in 'Done' status (as 'done' child issues should not have their fix versions changed after completion).

The releases / fix versions are below:

Fix Versions.png

The example Epics fix versions are below:

Fix Version Epic.png

The rule I've attempted to create is below:

Fix Version Automation Rule.png

When I create a new story under the epic, the audit log is shown below:

Fix Version Audit Log.png

Does anyone know what I'm doing incorrectly? I think it may be the Smart Value in the automation rule.

Thanks for your help.

Chris

Accepted answers

Bill Sheboy

Hi @Christopher Vickery

There is no list function "latest" to find what you asked.

Assuming the most recent / latest version is always the last one created, you could do this by the ID value (as that is required for the edit):

{{issue.fixVersions.id.max}}

If not, things get more complicated...

Instead you would need to find the maximum releaseDate value in the list of versions selected, and then use dynamic searching methods to extract the ID value:

find the maximum releaseDate with {{issue.fixVersions.releaseDate.max}}
use that to build a dynamic regular expression
expand all the selected values in the Fix Versions field, keeping at least the ID and releaseDate
filter #3 above using inline iteration, the match() function, and the regular expression from #2 above
split apart the result to get the ID

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Christopher Vickery

There is no list function "latest" to find what you asked.

Assuming the most recent / latest version is always the last one created, you could do this by the ID value (as that is required for the edit):

{{issue.fixVersions.id.max}}

If not, things get more complicated...

Instead you would need to find the maximum releaseDate value in the list of versions selected, and then use dynamic searching methods to extract the ID value:

find the maximum releaseDate with {{issue.fixVersions.releaseDate.max}}
use that to build a dynamic regular expression
expand all the selected values in the Fix Versions field, keeping at least the ID and releaseDate
filter #3 above using inline iteration, the match() function, and the regular expression from #2 above
split apart the result to get the ID

Kind regards,
Bill

Christopher Vickery

Hi Bill,

Thanks for getting back to me about this.

I've updated the Variable Smart Value to '{{issue.fixVersions.id.max}}' as you suggested.

Unfortunately the most recent created fix Version is still not being added to the newly created child issue.

The audit log is below:

Fix Version Audit Log (2).png

It looks like the branch rule / related issues can't be found for some reason. Which is strange as the branch goes out to the 'children' as expected.

Do you have any other ideas how I can get this working?

Also, thanks for sharing the more complicated resolution. I'm not expert enough to try this!

Thanks,

Chris

Bill Sheboy

What the audit log shows is the rule is not finding any child issues, so I am unclear what you mean...and that seems unrelated to copying the Fix Version value.

And reviewing your original rule image, one of the conditions checks if the trigger issue is an Epic, Story, Sub-task, or Task...but Sub-tasks cannot have children.

Let's confirm your scenario:

GIVEN a parent issue is an Epic, Story, or Task issue type
AND the parent issue has at least one value in the Fix Version field
WHEN an issue is created as a child of the parent issue
THEN copy the most recently created version from the parent issue's Fix Version to the child's Fix Version field

How does this compare to your scenario?

Christopher Vickery

Hi Bill,

Thanks for the quick response.

The scenario you've listed is exactly correct. The only additional point is that any existing children of the parent issue that are in 'Done' status should not have their fix versions amended.

So when a child issue is created in the screenshot below, the CSP-25.1 fix version is added to it:

Create Story under Epic.png

Nothing should change for the child issue already in 'Done' status.

The automation rule (including the '{{issue.fixVersions.id.max}}' smart value you recommended is below:

Automation Rule 1.png

Automation Rule 2.png

Thanks again for your help.

Chris

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

rule