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 rule for fixversions: Creating the same fixversion on another project

Nicole Radle

Hello Community,

We have a larger client with different departments.
We have created these departments as individual projects in JIRA.
Of course, the software is updated for all departments under the same release version.

Currently, I have to create the release version for each of the projects. Now I would like to create an automation rule for "Version created" so that the same version is also created in the other projects.

However, I fail completely with the syntax and hope for help.

Greetings

Nicky

Accepted answers

Julia Foden

Hi Nicky

You would use Version Created as the trigger. And then the action will be Create Version and you can use smart values like {{version.name}}, {{version.releaseDate}}, {{version.description}} to copy those values from the trigger version.

The Create Version action is in one project only so you will need to repeat the action for each project in which you want to create the version.

Bill Sheboy

Hi @Nicole Radle

It is possible for a version create in one project to create another version in a different project.

This would normally require a global/multiple project scope rule to allow the actions to span projects. You appear to be on the Jira Cloud, standard license level. If that is correct, please note there are limits to the number of executions per month for such rules, so consider how many versions you would have to learn if it would exceed your limits: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Kind regards,
Bill

All comments

Julia Foden

Hi Nicky

The Create Version action is in one project only so you will need to repeat the action for each project in which you want to create the version.

Bill Sheboy

Hi @Nicole Radle

It is possible for a version create in one project to create another version in a different project.

Kind regards,
Bill

Nicole Radle

Hi Bill,

yeah we have limits for global rules, but with the release version we won´t reach it. We are talking about maybe five release versions in three month, which should be copied then to 10 other projects.

Do you have an idea how I could create this rule?

Nicole Radle

Hi Julia,

thanks for your answer.
I will test it

Nicole Radle

Hi @Julia Foden ,

"copy" the fixversions to other projects works. Thank you very much for your help.
Now me and my team wanna update all simliar fixversions when one is changed.

So I choosed the trigger "when version updated" but there is no action to say update version.
Do you have any ideas?

Julia Foden

Hi @Nicole Radle

No, I wanted this myself but 'Update version' does not exist as an action.

Sometimes as a workaround if the thing you want to do does not exist (yet) as an automation action, you can do 'send a web request' to Jira's REST API. There is an API for Update Version but it requires the version id. In your case you would have the name but not the id so I can't think of a way of making this work.

Bill Sheboy

As site admin, you should be able to create a global/multi project scope rule, and it may be as simple as:

trigger: version created (possibly adding some limits on the ones triggering this)
action: create version in the target project

For this rule, ensure you do not enable the "Allow Rule Trigger" option, or this rule could trigger itself in a loop.

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