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 set rule automation to not create a linked issue if one is pre-existing

Stephen Johnston_dldj4j

I have a rule automation set up in my project that creates a test ticket in the Zephyr project

I am trying to set it up so if I transition the same statuses again the rule will not create another linked issue if it already exists

New test ticket has the following naming convention for the summary field . The goal of step 4 below is to not create the Zephyr test if there is already a linked ticket

{{Issue.key}} - {{Issue.Summary}}

Workflow

Auto Steps.png

Step #4

Auto Steps Part to stop recreating.png

Accepted answers

Mikael Sandberg

Your JQL is missing "" around the text you want the search for, and I would do a specific search like this:

summary ~ "\"{{issue.key}} - {{issue.summary}}\""

By using "\" \"" the search will only be for that phrase, not any of the words.

All comments

Mikael Sandberg

Your JQL is missing "" around the text you want the search for, and I would do a specific search like this:

summary ~ "\"{{issue.key}} - {{issue.summary}}\""

By using "\" \"" the search will only be for that phrase, not any of the words.

Stephen Johnston_dldj4j

I made that update but it still creates another linked issue

Bill Sheboy

Hi @Stephen Johnston

Yes, and...to the suggestions from @Mikael Sandberg

I sometimes find that related work items condition with links and JQL produces inconsistent results when checking for the absence of work items. My hypothesis is we do not how the rule implements those two checks together for linking and the JQL, thus it may not be what was intended.

As an alternative building on Mikael's suggested change to the JQL with the exact match syntax, I recommend using the Lookup Work Items action to take better control of the rule steps. For example, with changes to your rule steps:

trigger: work item transitioned...
condition: project is one of...
condition: issue type equals Story
action: lookup work items, with JQL of

issue IN linkedIssues("{{issue.key}}")
 AND summary ~ "\"{{issue.key}} - {{issue.summary}}\""
 AND issueType = Test

smart values condition:
- first value: {{lookupIssues.size|0}}
- condition: equals
- second value: 0
action: create a new Test...

Kind regards,
Bill

Stephen Johnston_dldj4j

Thanks Bill

It run successfully but it didn't create a Ticket in the Zephyr project

Work item transitioned
09/03/2025, 17:03:55

xxx-63858: Test zephyr new approach
Quality Assurance
Work item fields condition
09/03/2025, 17:03:55

The following work items passed:
xxx-63858
Work item fields condition
09/03/2025, 17:03:55

The following work items passed:
xxx-63858
Lookup work items
09/03/2025, 17:03:55

A search during custom value definition found no work items.
{{smart values}} condition
09/03/2025, 17:03:55

The following work items did not match the condition:
xxx-63858

New Workflow.png

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