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

Jira automation - how to 'promote' fixVersion to Parent matching children fixVersions with regexp

Michał

Hey,

the trickiest automation I've seen till now ...

Could help?

There is UberEpic issuetype which has linked Epics.
Epics get fixVersions for quarters: DUN YYYY QX eg. "DUN 2024 Q1", "DUN 2024 Q2"
Epics can have different fixVersions

I'm trying to fulfill this conditions:

If all linked Epics has the fixVersion for quarter set, add latest for UberEpic.

If any of the Epic has missing fixVersion for quarter, remove quarter from UberEpic.

I got to situation where automation can

1. find find UberEpic

2. check if all linked Epics have fixVersion with pattern using 'related issue condition' with JQL: issueFunction in linkedIssuesOf('{{issue.key}} and issueLinkType = "Is a Parent of" ') AND issuetype = Epic

tricky part:

3. find latest quarter from all fixVersions in linked Epics?

could I use 'Create Variable' with some magic in it?

that's my current state of rule:

Accepted answers

All comments

Jason Chayer

@Michał - unfortunately I do not have an answer to your question. However, curious where you got the issuetype UberEpic?

I would love to utilize this issuetype as linking Epics to a master project would be very beneficial.

Michał

Hey @jas ,

in big Jira project of big Organization of name I shouldn't share publicly. UberEpis is just my 'code name'

This is just another Issuetype - you can create number of 'custom' issuetypes. It would better to use 'Jira portfolio' hierarchy with 'Initiatives' instead but I need some time to fix this and other config issues in this particular project.

Jason Chayer

Ok, that makes sense. I finally ran across an article that mentioned "initiatives," I will take a look at that.

Thanks.

Bill Sheboy

Hi @Michał

Without seeing your entire rule and audit log details for context...

Have you tried using the max function on the list of fixVersion's date attributes to find the last one:

https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html#Jirasmartvalueslists-list.maxlist.max

Kind regards,
Bill

Michał

Hey @Bill Sheboy

direction is very good. Is there a way to create a list of fixVersions from multiple issues? Or iterate every issue from jql ?

Automation should find max of versions in all children of issue.

Thank you for your fast answer! I'll put schema tomorrow.

Thank you

Michal

Bill Sheboy

The answer depends upon what you want to do with the result, and which attributes of the version to access. Seeing the specifics of your rule will help suggest more ideas.

With multiple versions assigned to each issue, this can get messy fast, and so you may need to experiment to learn how possible this scenario is.

For example, using list iterators, all of the fix versions spanning multiple issues could be concatenated into a single CSV list, split back into a list, reduced with distinct, and then filtered to one value with max on the release date attribute...storing that in a created variable. Then that variable could be used to create another variable for a dynamic match() expression, which is finally used with in-line iteration to get the desired version.

I am using Jira Cloud, not Data Center, and so I cannot test how much of this is possible with that version of automation rules.

Michał

I can see could have more advanced functions.

Here are pictures of hierarchy build on links.

and rule I got till now.

Michał

no problem,

it can be really challenging to tailor everything right and make it work smoothly :-) every company I join there is really much to let all work easier in more automated way

Welcome!

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

Quick Links

Find more posts tagged with

jira

automation

data-center

jira-software-data-center

fixversion