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 to create and update a fix version in child issue projects when added to Epic

Shannon DeVico

I am trying to create an automation within a group of Projects that normally work together on tickets and need the same Fix Version.

- The automation is set up for multiple Projects (Project A, Project B, Project C, Project D)
- Goal of the automation is: when a fix version is created and updated on the Epic in Project A (or B or C or D) it will then create the same fix version in the projects of the stories in the Epic and update the stories

I have successfully been able to get the fix versions created and updated to the stories in the Epic but it is not creating the fix versions ONLY in those child story projects, it creates the fix version in ALL projects in the Automation.

Example:
- Epic in Project A has linked stories in Project A and Project C
- Epic get's a FV added
- FV is then created in Project A, B, C, D
- Story in Epic in Project A and Project C get fix versions updated

Is there a way to limit the FV creation only to project A and C (in this example) ? Below is my test automation where I was trying to get it to only associate projects from tickets linked to a specific Epic. It still creates in all Projects. Screenshot 2024-04-22 at 6.53.39 PM.png

Accepted answers

Bill Sheboy

Hi @Shannon DeVico

First thing, I am using Jira Cloud and not Data Center, and so my suggestions are based on what I know about rules, and not Data Center version. With that out of the way...

In the Create Version action, which project did you select: Same Project, Same Project as Trigger, something else?

When I tried this with Same Project selected, the scope was limited and only created the new version in the project from the issue for the branch-to issue.

Also, how many issues in each project (A, B, C, D) are you expecting to be child issues of that epic? If it is multiple, wouldn't this rule try to create multiple versions with the same name?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Shannon DeVico

First thing, I am using Jira Cloud and not Data Center, and so my suggestions are based on what I know about rules, and not Data Center version. With that out of the way...

In the Create Version action, which project did you select: Same Project, Same Project as Trigger, something else?

When I tried this with Same Project selected, the scope was limited and only created the new version in the project from the issue for the branch-to issue.

Also, how many issues in each project (A, B, C, D) are you expecting to be child issues of that epic? If it is multiple, wouldn't this rule try to create multiple versions with the same name?

Kind regards,
Bill

Shannon DeVico

Hi @Bill Sheboy

In the Create Version action, which project did you select: Same Project, Same Project as Trigger, something else?

- I have Current Project selected as the other options are the list of specific projects and you can only chose 1

Also, how many issues in each project (A, B, C, D) are you expecting to be child issues of that epic? If it is multiple, wouldn't this rule try to create multiple versions with the same name?

- From what I can tell across these projects (There are 5 that work together frequently) - 3 are the main Epic creators and 2 or 3 of the teams will have 1 - 4 child tickets within the Epic. When I tested it with my manual test automation it did not create duplicates.

My only other thought if I could not find a way to condition it to only create the fix version in the child ticket projects is to have an additional follow on automation to delete the blank FVs after.

Shannon

Bill Sheboy

It appears the action options are different for Create Version between Cloud and Server / Data Center apps.

Regardless, this seems like a bug to me as the current scope in the branch should determine the "current project". After a quick search, I could not find a similar defect in the public backlog. I recommend working with your Jira Site Admin to contact Atlassian Support to learn what they suggest.

Until you hear back from them...

As a workaround, instead of using that rule action you could try calling the REST API function to create a version using the Send Web Request action, specifically providing the project name / key.

If you want to try that, here is a how-to article for calling a REST API function from a rule, and the function you may need:

https://community.atlassian.com/t5/Jira-Software-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/version-createVersion

Shannon DeVico

@Bill Sheboy Thank you! We will reach out to our Admin and try the workaround. Appreciate all the help!

Welcome!

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

Quick Links

Find more posts tagged with

jira

version

automation

data-center

fix-version

jira-software-data-center