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

Add fixversion as label using Automation, without changing/removing existing labels

M0214104

It always overwrites instead of adding - what has to be changed, so it does not. I tried several ways...

Accepted answers

Fazila Ashraf

Hi @M0214104

Replace the smartvalue in your screenshot with {{issue.fixVersions}}

Additionally refer to 'To edit the field without overwriting its original content:' section of https://support.atlassian.com/automation/kb/how-to-update-a-select-field-multiple-from-the-content-of-other-fields/

All comments

M0214104

also not working

M0214104

based on https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Bill Sheboy

Hi @M0214104

For a question like this, context is important for the community to help. Please post the following:

what version of Jira are you using: Cloud, Server, or Data Center
for Cloud, what type of project is this: company-managed, team-managed, JPD, etc.
an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution

Until we see those...

The Fix Versions field has a list of values in the smart value {{issue.fixVersions}}

https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-issue.fixVersions

Thus you may need to use advanced edit with JSON to add the values from that list:

https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html#AdvancedfieldeditingusingJSON-Addinglabels

And, you do not describe what is in your version names. For example, if there are spaces those will not work with labels. They need to be replaced, such as with underscores.

Putting that all together, you could use this dynamic JSON expression to add the labels:

{
  "update": {
    "labels": [
      {{#issue.fixVersions}}
        {
          "add": {{name.replace(" ", "_").asJsonString}}
        }{{^last}}, {{/}}
      {{/}}
    ]
  }
}

Please adjust this based on the actual content of your version names.

Kind regards,
Bill

Fazila Ashraf

Hi @M0214104

Replace the smartvalue in your screenshot with {{issue.fixVersions}}

M0214104

Hi @Bill Sheboy and @Fazila Ashraf

We're on Data Center.

Our Release Versions contain an underscore, e.g. PI_25Q4W

I have changed the smartvalue as the additional information, as given above.

Image of the complete automation:

Issue before Automation:

Audit log says it is successful - which it is, it has set the label. BUT it also did overwrite!!!

Issue after Automation:

Why does it do this? It's so not logical, in a bulk change it is possible to add and still have the labels from earlier on.

Thanks so much for your help

Bill Sheboy

When using the Edit Issue action, a field may be selected from the dropdown list or updated using JSON with "additional fields"...but not both in the same action.

And...I note you changed the dynamic JSON to use both single and double-quotation marks. That will not work, and it is why I used the asJsonString function:

{{name.replace(" ", "_").asJsonString}}

If you are certain your version names will never contain spaces, you may simplify what I suggested earlier to remove that logic:

{
  "update": {
    "labels": [
      {{#issue.fixVersions}}
        {
          "add": "{{name}}"
        } {{^last}}, {{/}}
      {{/}}
    ]
  }
}

AND, I fixed a typo from my earlier post as it was missing the pound sign # in the iterator. Please add that to your expression.

Please deselect the field from the dropdown list, update the expression, and re-test. Thanks!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

datacenter