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

Automate addition of a label when issue is linked

Nico_hfm0e0

Hello everyone,

I'm trying to set up an automation, but I can't find how to fit my requirement.

I need that :

When a ticket A from any project is linked to a ticket B from a project X, and ticket B has a label = Test123, then ticket A must have a label Test456.

Thank you for your help,

Nico

Accepted answers

Varsha Joshi

Hi @Nico

You could try using the following:

Hope this helps.

All comments

Varsha Joshi

Hi @Nico

You could try using the following:

Hope this helps.

Bill Sheboy

Hi @Nico

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

First thing, you appear to be on a Free license level. If so, that means you have a 100 automation "usage" limit per month: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits

The rule you describe will need global-scope, and thus you may quickly consume that limit, and so halt further rule execution for the remainder of the month.

Assuming that is acceptable...

As noted, your rule will need global-scope, triggered on Issue Linked, and then it could test the trigger issue is in your "project X" using a condition. The remainder of the rule should be easy to implement after that.

Kind regards,
Bill

Nico_hfm0e0

Hi @Varvara ,

Thanks for your reply
We ended up doing something like this, and it works.
The only remaining problem is that I only have to update the "Is child of" issues.
Unfortunately, when I start a branch, if I put a filter on the link type, it doesn't find any related issue.

It works perfectly when I remove the filter.

As my client has 2 links with the same "is child of" name, I imagine this may be the source of my problem.

Thank you,

Nicolas

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