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

How to add multiple fix versions to an issue?

Yue Pan

Appreciate any suggestions!

I'm setting up an automation such that when an issue status is transitioned to Done, multiple releases are added to the issue's fix version field.

For context, in our project, we have 8 different releases that map to different work streams. I only want to add a subset(4) of releases to the issue fix version, which is differentiated by an ID in the release name.

Currently I have for-loop which iterates through all the releases in the project. If a release with the ID is found, then update the issue's fixVersion by adding the release.

According to the logs, the 4 releases are consistently identified correctly. However, sometimes not all 4 releases are added as fix versions. It seems to happen randomly, sometimes 4 get added, sometimes 3 and sometimes 2.

Wondering why the Edit Issue Fields action is not executing consistently every iteration when the conditions are met? Is there an order of operations problem, where editing an issue field multiple times in the same automation will cause race conditions? Is there an alternative set-up that would work better?

Screenshot 2024-11-15 at 3.20.46 PM.png Screenshot 2024-11-15 at 3.22.33 PM.png

Accepted answers

Bill Sheboy

Hi @Yue Pan -- Welcome to the Atlassian Community!

Automation branches which could be on more-than-one-thing are executed in parallel and asynchronously, with no guaranteed processing order and that the branch may not finish until the last step of the rule.

What this means for your rule is the edits are sometime colliding / walking over the updates from each other.

For your scenario, the solution is to gather all of the releases to add and perform a single update with JSON to add them together. This can often be done with created variables, list filtering, etc.

If you show your complete rule in a single image, that will help the community advise you how this may be accomplished for your scenario.

Kind regards,
Bill

All comments

Jim Knepley - ReleaseTEAM

Welcome to the community, @Yue Pan

You may be bumping up against an API rate limit, but I'm not sure how to check for that in Cloud sites, in Data Center, you can look at the audit log.

Bill Sheboy

Hi @Yue Pan -- Welcome to the Atlassian Community!

What this means for your rule is the edits are sometime colliding / walking over the updates from each other.

For your scenario, the solution is to gather all of the releases to add and perform a single update with JSON to add them together. This can often be done with created variables, list filtering, etc.

If you show your complete rule in a single image, that will help the community advise you how this may be accomplished for your scenario.

Kind regards,
Bill

Yue Pan

Thanks Bill! I read in an older thread that advanced branching executes async, but not regular branching, so that's a bummer.

Do you mind providing some guidance of how I might use a single JSON to achieve this? My biggest hurdle is finding a way to filter the list of {{project.versions}} to find the releases that meet my criteria.

I explored creating an array and appending desired releases to it, but didn't find any good resources for how to achieve that.

I also looked into using smart values with this function, but it didn't seem to log anything:

{{#project.versions}}
  {{#not(archived)}}
    {{#not(released)}}
      {{#name.startsWith("ID")}},
      {{/}}
    {{/}}
  {{/}}
{{/}}

Below is my entire rule, as well as the definition I'm using for advanced branching. Screenshot 2024-11-18 at 10.23.39 AM.png

Bill Sheboy

The project versions are not directly available like that in a rule. Instead they may be found for ones associated to an issue (e.g., as Fix Version values) or by calling the REST API endpoint using the Send Web Request action.

From what you describe, I believe you will need to call the REST API and send the necessary filtering parameters:

For example:

yourJiraURL/rest/api/3/project/yourProjectName/version?orderBy=name&query=ID&status=unreleased

Once you have those results in the web response, it may be filtered further using your check to start the name with "ID", and then finally iterate over the result to create the JSON. This will take several steps:

create variable: Make a list of the names from the web response, filtering them, and adding a delimiter of ~~
- name: varNameList
- smart value:

{{#webResponse.body.values}}{{#if(name.startsWith("ID"))}}{{name}}~~{{/}}{{/}}

create variable: Dynamically build the JSON by iterating over the previously created variable.
- name: varJSON
- smart value:

{
  "update": {
    "fixVersions": [
      {{#varNameList.substringBeforeLast("~~").split("~~")}}
        { "add": { "name": "{{.}}"} } {{^last}},{{/}}
      {{/}}
    ]
  }
}

Use {{varJSON}} in your edit action.

Yue Pan

Apologies for the delayed response. Thanks Bill! That worked wonders, wish we could make a feature request to have this more easily accessible.

As part of the varJSON, I was wondering if there is a way to simultaneously update the issue's status? I saw in the API docs that you can update statuses via another request, but would love to combine it altogether.

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

release

fix-version

release-management

jira-automation