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

Automation creating two stories, when I only have one in the automation

Corey Hemingway

My automation is creating two stories when I have only got the one in the automation, can you advise what I'm doing wrong here please

Automation:

Aduit Log: Showing two created (but with same Key ID?)

However, in release - its two different tickets?

Accepted answers

Corey Hemingway

I found the issue. I have 2 rules both using a similar trigger word (oops silly me)

I have Mobile | iOS and Mobile | Android and they are both triggering I believe due to the word mobile.

I didn't realise I can't use a string here. I tried to update using "" but this didn't work - any way to use a string in this? Or do I need to have a unqiue starting word?

All comments

Curt Holley

Hey @Corey Hemingway

I don't believe it is creating two stories with the same key (or even two stories at all). I've seen this also, but never found any evidence of the duplicate.

I believe it is just a quirk of the automations audit log.

Gor Greyan

Hi @Corey Hemingway

Maybe it can be for the following reasons:

- Triggered by multiple rules (a project rule and a global rule), or

- The rule’s scope includes multiple projects, or

- It’s re-triggering itself due to “Allow rule trigger” being enabled.

Please also check these points.

Bill Sheboy

Hi @Corey Hemingway

Based upon the work item keys shown in the audit log, this seems to be a timing problem of some type:

story PD-22708 is created
and when it is branched to as the most-recently-created item, the next key used for the sub-task is PD-22710...
which means the story PD-22709 was created in the time between those two steps, which appears to be over a time of around 2 seconds duration

Some things to check are:

Look at the history for PD-22709 to learn...
- who created it and when, relative to the other work items
- when it was assigned to the version you show
Look at the complete rule audit log to see if it triggered twice in rapid succession
If your rule has been edited / published several times, it could be "glitched", causing the duplication AND not logging it
- The way to check for this is to disable your current rule, and re-create it from scratch
- Then test to see if it has the same symptom

Kind regards,
Bill

Corey Hemingway

I found the issue. I have 2 rules both using a similar trigger word (oops silly me)

I have Mobile | iOS and Mobile | Android and they are both triggering I believe due to the word mobile.

I didn't realise I can't use a string here. I tried to update using "" but this didn't work - any way to use a string in this? Or do I need to have a unqiue starting word?

Curt Holley

Don't have spaces in the Release title. Go with something link Mobile_Android and make that the search criteria.
Or possibly, Leave the titles as is, but only search for Android and iOS. But that might not be enough??

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

jira-automation