How to create a Sub-task for each added Fix version

[Martin Karlsson]

What I want

A rule creating a new Sub-task when a Fix version is added to a Bug / Story (disregarding existing Fix versions in the Bug / Story), and the Sub-task should "inherit" the newly added Fix version.

If more than one Fix version is added a new Sub-task should be created for each one, and each one "inheriting" only one of the newly added Fix versions.

My rule

Main branch

Trigger: Value changes for the Fix version field.
If: JQL: issuetype in (bug, story)

Branch

For each Smart value: {{#changelog.fixversions}}{{toString}}{{/}} or {{#fieldChange.to}}{{fixVersions}}{{/}}, with Variable name: newFixVersions

Then: Create new Sub-task with Fix version: {{newFixVersions}} (and copying a bunch of other fields)

The problem

As noted I've tried using fieldchange as well as changelong but none of them work, at least not the way I want it to.

{{#changelog.fixversions}}{{toString}}{{/}}

This is what I tried first and it doesn't work at all: "The provided smart value couldn't be resolved to an object".

This surprised me a bit since I actually have another rule creating new Issues when Components are added to the Bugs / Stories (one Issue per Component added) which uses changelog exactly like this and it works like a charm. So I guess there's some under-the-hood difference between the Component and Fix version fields I'm not familiar with.

{{#fieldChange.to}}{{fixVersions}}{{/}}

Not quite right. It does read the changed Fix version field but goes on to create Sub-tasks for all Fix versions, i e already existing ones as well as the newly added ones.

Any idea on how to solve this?

[Bill Sheboy]

Hi @Martin Karlsson 

Short answer: what you are trying may not work because of known defects with the reliability of the Fix Versions field and the changelog available to automation rules.  If you still want to try this...

Advanced Branches take a list as a source value, but the value you are supplying is a text string.  You could try storing that with a Created Variable as a comma-separated values string, and then use split() to parse the variable into a list for the branch.

I recommend starting by creating the variable and just writing it to the log, with no branch to create the issues.  After you have a changelog expression which works reliably-ish, then add the branch with the split() variable to create the issues, perhaps using either the version ID to directly set the field, or JSON with the version name in advanced edit.

Kind regards,
Bill

[Martin Karlsson]

Hi @Bill Sheboy 

Thanks for the reply! Fairly advanced for my level but I'll have a go at your suggestion. 

[Martin Karlsson]

After googling the problem I tried something mentioned in https://jira.atlassian.com/browse/JIRAAUTOSERVER-207, using changelog but replacing "fixversions" with "fix version". Lo and behold, the solution was that simple. For me at least, as mentioned in that issue it seems other people have problems with that as well. Guess I lucked out on this one.

[Vishal Biyani]

@Martin Karlsson 

Can you try with {{issue.fixVersions.name}}?

To iterated through each version something like this is required

{{#issue.fixVersions}}

* Fix version: {{name}}, released on {{releaseDate}}

{{/}}

[Martin Karlsson]

Hi @Vishal Biyani 

Using the same setup as before I got the same results as with changelog: "The provided smart value couldn't be resolved to an object".

[Vishal Biyani]

Try with {{#issue.fixVersions}} {{ name }} {{/}}