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

Not running an automation again for - Linking Test issue type to its trigger issue

Nicola_bcuvb4

Hi there, I have an automation in place as screenshot below.

When an Issue has its Fix Versions field changed it should create a Test in the same project and link it to the Issue that triggered the rule.

But - How would I make sure the automation didn't run again if I made the Fix Versions field empty, but then repopulated it again?

So, not creating and linking a new test if the issue got moved to a different Fix Version.

Accepted answers

Jack Brickey

You could add a label when the rule runs that can then be tested for as a condition.

for example …

if labels does not equal “I-ran-before”

All comments

Jack Brickey

You could add a label when the rule runs that can then be tested for as a condition.

for example …

if labels does not equal “I-ran-before”

Nicola_bcuvb4

I see what you mean. It feels like adding another layer on top of the rule.

I am trying to think of some logic that looks like 'don't run the rule again if there is already a test linked', but I am not sure that is a thing.

I am going to have another think, but maybe you are right - adding a label at the time a test is created and linked and then using that label to not add another test if the issue is moved to another fix version, could be the way to go.

Jack Brickey

I think you can check for the existence of a linked issue. I recall doing that.

Jack Brickey

Try using Related issues condition

Welcome!

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

Quick Links

Find more posts tagged with

automation