Hello all, I have set up the following 2 automation rules: * If in the field Component/s the component name starts with E add #EMP to the Epic name * If in the field Component/s the component name starts with F add #FRA to the Epic name. This works well as long as there is only ONE component selected in the Epic. But if there are 2 components selected, one starting with "E" and one with "F", only #EMP is added to the iEPic name...but I want #EMP and #FRA to be added to the Epic name. Any idea how to solve this?

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

Adding a text string to an Epic Name depending on component's text

Daniel Schoeneck

Hello all,

I have set up the following 2 automation rules:

If in the field Component/s the component name starts with E add #EMP to the Epic name
If in the field Component/s the component name starts with F add #FRA to the Epic name.

This works well as long as there is only ONE component selected in the Epic. But if there are 2 components selected, one starting with "E" and one with "F", only #EMP is added to the iEPic name...but I want #EMP and #FRA to be added to the Epic name.

Rule #FRA2.PNG Rule #EMP2.PNG Rule #EMP1.PNG Rule #FRA1.PNG Problem_only #EMP.PNG
Any idea how to solve this?

Accepted answers

Bill Sheboy

Hi @Daniel Schoeneck and the community helping on this one!

You do not state the format of your epic name, so let's assume it is something like this:

EPICNAME [0 to many component indicators, prefixed by " #"]

Have you considered doing this in one step / edit action (without any conditions), using smart value list filtering? https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588

{{issue.epic name.substringBefore(" #")}}{{#issue.components}}{{#if(equals(name.left(1).toUpperCase(),"E"))}} #EMP{{/}}{{/}}

Please repeat the inner section for any component you want to handle

Also, you would need rules to make the update for different triggering events: issue create, components changed, epic name edited by other than rule, etc.

Kind regards,
Bill

All comments

Mark Segall

Hi @Daniel Schoeneck

From your screenshots, it appears you're using Jira Server automation, correct? If so this will be a little more tricky as you don't get the benefit of advanced branching. However, this could be possible and with a single rule.

Can you confirm whether the Epics will ever have more than 2 components?

Wouter van den Berg_xzpt7s

Hi @Daniel Schoeneck

UPDATE: Sorry, didn't see you are on server. I'll leave the answer for the people that end up here using Cloud.

I have tried a different approach. See screenshot:

Screenshot 2023-08-18 at 15.24.27.png

Refetch in the first step might not be needed but I always do it anyways. In my case I did the comment action to see if it works but have a go at this.

Goodluck.

Wouter van den Berg_xzpt7s

Ah didn't even notice that. Your approach would be {{issue.components.first.name}} and {{issue.components.last.name}} I presume?

Mark Segall

I was actually thinking more along the lines of

{{issue.components.name.get(0)}} and {{issue.components.name.get(1)}} but your approach will work too. 🙂

Daniel Schoeneck

Hi,

yes the Epics can have an unlimited number of components

Wouter van den Berg_xzpt7s

I can see your predicament. When there is a lot of changes you don't want to go back in and change the rules each time. Maybe you could extend the solution provided above with a regular expression. I don't remember if Server supports this but I assume it does. Use the branching logic that @Mark Segall provided but instead of component in you could use:

^[eE] for matching components starting with e or E
^[fF] for matching components starting with f or F Screenshot 2023-08-18 at 16.15.12.png

Bill Sheboy

Hi @Daniel Schoeneck and the community helping on this one!

You do not state the format of your epic name, so let's assume it is something like this:

EPICNAME [0 to many component indicators, prefixed by " #"]

{{issue.epic name.substringBefore(" #")}}{{#issue.components}}{{#if(equals(name.left(1).toUpperCase(),"E"))}} #EMP{{/}}{{/}}

Please repeat the inner section for any component you want to handle

Also, you would need rules to make the update for different triggering events: issue create, components changed, epic name edited by other than rule, etc.

Kind regards,
Bill

Mark Segall

Ha - I should've known that Mr Sheboy would come in with a more elegant approach! 🙂

Daniel Schoeneck

Thanky you @Bill Sheboy
Never thought about that...or let's say: I did not know that this is possible I don't even understand how this code works and how to implement into my automation rule

What would be the advantage of your solution?

Wouter van den Berg_xzpt7s

Way cleaner solution definitely. The advantage here is a cleaner solution, less load for automation and no conditions that need matching before execution.

The disadvantage was made clear the moment you replied. This is definitely more advanced. Upon you leaving the system, the one replacing you will probably have some questions how the logic works.

Thanks for sharing this clean solution @Bill Sheboy

Welcome!

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

Quick Links

Find more posts tagged with

automation