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 to create an idea in a status fails

Donni Shimanovich

I am trying to create issues not in the Parking Lot. Workinng for a start up, I often recieve ideas which we need to begin next sprint, hence I would like to create the ideas in the "next sprint" status.

I have a custom field, called "Roadmap" which one-for-one aligns with my status. I have this so that I can color-code my cards. It seems like I cannot color code statuses.

I then wrote automation, when an idea is created, if roadmap equals "Next Sprint", then transition the status to Next Sprint.

rule details.png

This automation never works, it always turns up with this transition issue:
transition issue.png

As depicted above, I've tried turning on the regex button but that doesn't seem to solve the issue.

Accepted answers

Mohanraj Thangamuthu

Hello, Good day. You are manually able to transition the issue ?

Also make sure that there is no condition in the workflow transition.

All comments

Mohanraj Thangamuthu

Hello, Good day. You are manually able to transition the issue ?

Also make sure that there is no condition in the workflow transition.

Mohanraj Thangamuthu

Also try only the transition to next status without any further actions.

Screenshot 2024-12-26 at 3.58.43 PM.png

Donni Shimanovich

Yes, I can manually transition the issue from any status to any status. The automation only looks at the "Roadmap" field and transitions the issue, there are no further actions in the automation.

Mohanraj Thangamuthu

From the screenshot that you have shared above, I see that you have selected "transition match". Could you try disabling this?

Bill Sheboy

Hi @Donni Shimanovich -- Welcome to the Atlassian Community!

There is a known, racetrack error with the Issue Created trigger. That is, the trigger can fire so quickly some issue data is not available to the rule yet. This often leads to missing data and unusual rule errors. I wonder if what you are observing is a case of this defect.

The fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit and re-load the data before proceeding.

Perhaps try adding that action after the trigger to observe if it helps with the issue transition.

Kind regards,
Bill

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-product-discovery