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

Destination status could not be resolved... Error is seen whenever i apply a rule from the library

Arham Sohail

"Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)"

I created a simple rule stating if all subtasks are done mark parent as done but I am experiencing the mentioned issue. I have checked the workflow it includes all the statuses I am changing, I am the automation actor but I am not the JIRA admin I am the Project lead. Is it related to Admin access or its something else? kindly help

Accepted answers

All comments

Dirk Ronsmans

Hey @Arham Sohail and welcome to the community!

As long as the automation actor (being you) is able to do it manually the permissions should be fine.

Best practice is to use the Automation for Jira user tho as it often has more rights/permissions.

As you applied the rule from the library a good thing is also to re-select the statusses in your automation rule. Behind the name of the status there is an internal id as well. If that is different than the one from the library (which probably is the case) it would set the correct one.

Also make sure that the transition between the current status and the one you need to go to exists and you are able to transition manually

Nic Brough -Adaptavist-

This error can be caused by two other things, and when it is that, the error message is misleading -

@Dirk Ronsmans check on will establish one case where there are conditions blocking the transition (but I'd actually expect a "conditions not met" warning in that case)

The other one gives you the misleading message that the status id is not valid, when it actually means "there is no transition from the current status to the requested one".

Can you check that there is actually a transition linking the two? (And check if there any conditions).

An "all" transition does count here - automation and all the "transition issue" scripts that work off a target status ID rather than the transition id I know will use an "all" transition if they find one.

Arham Sohail

Hey, @Dirk Ronsmans thank you for the response.

Sure will ask my admin and will try with the total admin rights too. I have tried with the reselecting statuses in the rule fix and still experiencing the same issue. As far as the transition is concerned I am changing statuses according to the workflow. Below is my manual transition & attached is the workflow:

Backlog>Ready for Dev>In Progress>Ready for QA>In QA>Done

https://jmp.sh/ydRqfmG

Dirk Ronsmans

And the transition to Done is that an All transition? (the screenshot cuts of right there)

Could you maybe share the automation itself?

Arham Sohail

Sorry for the inconvenience, yep Done after In Qa is in my workflow. Please find the required Screenshots.

Done Workflow: https://jmp.sh/N8vfypj

Automation Rule: https://jmp.sh/HcZRq3B (When Parent done mark all subtasks as done)

Arham Sohail

@Nic Brough -Adaptavist- Thanks for the response, how can i exactly check if the transition is linking the two? I am using the rule from jira automation library & i haven't added any conditions.

After the transition is done I am adding a comment on the parent issue that I am marking this as to be done(PFA screenshots). The comment is being added but the transition from backlog to done is not being done.

https://jmp.sh/qwV5reI

Nic Brough -Adaptavist-

Look at the workflow.

An Automation can not transition an issue to a new status if there is no transition between them in the workflow, or there are blocking conditions on the transition (not automation conditions, workflow conditions)

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

jira-service-management-cloud

jira-service-management