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

Jira Rule Automation Error: Destination Status Could Not Be Resolved: How do I resolve this error?

tyrone kimble_33sofe

JIra Rule Issue.png

Accepted answers

Niranjan

Hi,

If you are using smart values, try with the status id instead of status name.

All comments

Niranjan

Hi,

If you are using smart values, try with the status id instead of status name.

tyrone kimble_33sofe

Thanks, How do I find the status ID?

Niranjan

Restapi call shoud display the statuses of an issue

/rest/api/2/issue/CPEC-123 should display the info

/rest/api/2/status should list all the existing statuses in your Jira

tyrone kimble_33sofe

Thank you!!!!

Con O'Connell

One of the behaviors I discovered in looking at this is when an issue is manually transitioned (so it is already in the destination status).

I added a condition to verify the current status is expected. For example, in TO DO before automatically transitioning to IN PROGRESS when a branch is created.

ENHANCEMENT REQUEST for the TRANSITION rule:
Built-in automation check should be if the issue is already in the DESTINATION status, just don't fire like some of the other built-in automation rules. The audit log should show "issue already transitioned" or something similar.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud