automation: Add fix version to existing fix version when creating task

[Dominique]

I found out how to create a version (depending on the issue.summary) and then how to add it to the issue just created. 

Now I want to also add the version of the parent task. 

My Problem: When I create a task without parent (link epic) it works perfect. The new version is created and added.

When I create a task with an epic link I see who the first version gets deleted and the version of the parent is added. 

Although I marked "Add to existing version" in the change issue field for versions.  

[Dominique · Accepted solution]

It is important to choose "Add Fix Version" and not "Copy Fix Version". In fact I did everything right. The If/Else part before this was too complicated and partly wrong. 
Therefore I made a separate rule and now it works. 

[lila]

Hey there, i dont have those options, just "last release version" and i added {{version.name}} - this does as you encountered initially - replace the previous fix version rather than adding the new one. Any tips? 

[Bill Sheboy]

Hi @lila 

As this thread is quite old, I recommend creating a new question and linking back to this thread.  That will ensure more of the community sees it to offer suggestions.  Otherwise only the people following this older thread will see it.  Thanks!

Until we see that question...

Did you notice the ... options to the right of the Fix Versions field when it is selected with the edit fields action?  If you select the ... and then Copy, those other options will be available.

Kind regards,
Bill

[lila]

Hey Bill, you mean in the dropdown? i dont have those options :




And the "..."either 



Ive added some code under more option ...  hopefully this would help? 

[Bill Sheboy]

When editing a field, you cannot use both the selection from the drop-down list and the JSON edit.

What value(s) are you trying to set in the fix version field?

[lila]

I want to add the last released version which is set as {{release.version}} 

[Bill Sheboy]

Is that a custom field as it is not a built-in smart value for {{release}}?

Please post an image of your complete automation rule, the details of any actions, and the audit log details showing the rule execution.  Those will provide context so we are aligned on how / where you are trying to update the Fix Versions field.  Thanks!

[lila]

Hey Bill, sorry about the delay - see below 

[Bill Sheboy]

Thanks for that information, @lila 

When editing a field with that action, you may only use the field from the drop-down list or edit with JSON.  You cannot do both in one edit action.

Do you want to replace the value in the Fix Version field or to add values to it?

• if replace, use the dropdown field method, and  clear out the JSON section
• if add, use the JSON section and remove the field from the dropdown by de-selecting it

[lila]

Amazing!!  I want to add not replace. Should i use (our versions are version.name format)

{
"update": {
"fixVersions" : [
{
"add": {
"name": "{{fixVersionName}}"
}
}
]
}
}

or 

{
"update": {
"fixVersions" : [
{
"add": {
"name": "{{version.name}}"
}
}
]
}
}

[Bill Sheboy]

If you are trying to add the version from the trigger, please use the second one:

{{version.name}}

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions

[NC]

Hi @Bill Sheboy

I am trying to do something similar I'm working on setting up a Jira automation rule aimed at appending the latest released version to the "Affects Version/s" field of all unresolved bugs that weren't part of the current release. See image below, however I am getting an error that the affects version is not adding the shipped version. The 2nd edit that updates the fix version to the next scheduled version works.

[NC]

How to Append New Version to "Affects Version/s" F... (atlassian.com)

[Bill Sheboy]

@NC -- I will respond in that other thread as this is a new question.

[Bill Sheboy]

Hi @Dominique Hermens 

Would you please post images of your complete rule and the audit log showing details of the execution that does not work as you expect?  That additional context may help the community to offer ideas.  Thanks!

Kind regards,
Bill

[Dominique]

Hey Bill,
I do not know what the problem was exactly but maybe I had to many "if/else" cases is this rule, so I just made a new rule with only this part and it works...

[Dominique]

Can I delete this question somehow?

[Bill Sheboy]

Hi!  I don't know how to do that, but instead you could:

add your own answer to explain, and then mark that one as "solved".

[Núria Rull Bassols]

not the right post