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

(Automation) With a manual trigger, how can I update all issues in a version?

Maroline Johnson

I'm trying to create an automation that will transition all issues in a version upon a manual trigger. For context, my organization will add to the Fix versions field when an issue's changes are merged to the version's branch. When we're preparing to release a version, we first do regression testing. I would like to use what's in the Fix versions field to transition all issues in a version from Status 1 to Status 2.

I've tried the following automation, but it's not working for me. The automation just won't run.

1. Manual trigger with user input - text field "Version Name", variable name is {{testingVersion.Name}}

2. Branch rule - For: JQL ({{userInputs.{{testingVersion.Name}}}} IN {{issue.fixVersions.Name}})

a. Condition - status equals Status 1

b. Transition issue - destination is Status 2

Could anyone please help me to figure out why this is not working? Or perhaps there is a better approach?

Accepted answers

Maroline Johnson

Big thanks to @Bill Sheboy for helping me out. There were a few issues.

1. The Variable Name in the trigger's input field had curly brackets around it, but it should not.

2. I was expecting the trigger issue to be transitioned, but the rule was set up so that only related issues were transitioned, and there were no related issues while testing.

All comments

Mark Segall

Hi @Maroline Johnson

You should be able to accomplish this with something similar to what you're already trying though I'm not quite sure what you're trying to accomplish with the variable:

TRIGGER: Manual

BRANCH (JQL)

fixVersion IN (YOURVERSION) AND status = status1

ACTION: Transition Issue (to status2)

Maroline Johnson

Thank you for your help @Mark Segall

I tried this, and I'm still running into the same issue where the automation just won't run.

The variable is meant to capture the name of the version which is being tested. We might have multiple versions that are unreleased, and I want this automation to run only for issues in a particular version. The Version Name input needs to capture the version that we want this automation to run for.

Bill Sheboy

Hi @Maroline Johnson

Adding to Mark's answer:

For a question like this, please include images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions.

Until we see those...

What do you mean by "the automation just won't run"?

Does your version name contain spaces or other non-alphanumeric characters? If so, please try modifying the JQL Mark suggested as follows, narrowing the rule scope and handling the characters in the version name:

project = {{triggerIssue.project.key}}
 AND fixVersion IN ("{{userInputs.testingVersion}}")
 AND status = status1

Kind regards,
Bill

Maroline Johnson

Hi @Bill Sheboy

Here are those images. I hope they help.

Start regression automation.jpg start regression automation audit log.jpg

I meant "the automation just won't run" as in - I would try to trigger the automation from an issue, and instead of running, a pop-up appeared that basically said "Oops, we can't run this automation." I've fiddled with it a bit more, and it's running now, but I can't say for sure what I changed to get it to run.

In this sample project, the versions do have a space, so I added the parentheses and quotes. I tried double quotes and single quotes. In the audit log screenshot, you can see now what's causing errors.

Maroline Johnson

Big thanks to @Bill Sheboy for helping me out. There were a few issues.

1. The Variable Name in the trigger's input field had curly brackets around it, but it should not.

2. I was expecting the trigger issue to be transitioned, but the rule was set up so that only related issues were transitioned, and there were no related issues while testing.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud