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

How to create automation- When x epic link is tagged, then x add component

Alyssa White

When an issue is updated
And If that update is the Epic Link being created
And if the Parent matches “component in (“test”)
Then Edit Issue add Component value(s) you want.

I would like to create an automation for when a story is tagged with a certain epic link, then a certain component is automatically added. I know this is close, but the automation still isn't working.

Can anyone give me some guidance on this?

Accepted answers

Mark Segall

Hi @Alyssa White and welcome to the community!

I'd recommend something like this:

TRIGGER: Field Value Changed (Epic Link)
This is less noisy than Issue Updated
CONDITION: Epic Link Is not Empty
IF CONDITION (Related Issues Condition)
- Epic
- Matches Specified JQL
- ```
Component IN (Test)
```
- ACTION: Edit Issue Fields (Component)

All comments

Mark Segall

Hi @Alyssa White and welcome to the community!

I'd recommend something like this:

TRIGGER: Field Value Changed (Epic Link)
This is less noisy than Issue Updated
CONDITION: Epic Link Is not Empty
IF CONDITION (Related Issues Condition)
- Epic
- Matches Specified JQL
- ```
Component IN (Test)
```
- ACTION: Edit Issue Fields (Component)

Alyssa White

Thanks so much @Mark Segall this works great!!

Alyssa White

@Mark Segall follow up question- do the components need to have the same name as the epic link I am trying to tag?

For example, I am trying to take this rule across my whole project for different epic links/multiple components-

When a story is tagged with the epic test123, then add components test1 and test345

I guess I'm having a hard time understanding what aspect of the rule is tied to the 'Epic Link' name since in my previous example they both had the name 'test'

Mark Segall

Not sure I understand. The rule condition is looking at the triggered issue's Epic to validate attached component(s) and if it returns true then applies whatever components you've defined to the trigger issue.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation