Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric s

Hizkeel Khan
Contributor
October 5, 2023

Hi,

I know this questions has been asked and I have read but I wasn't able to find any solution for my problem. 

I have two separate workflows:

  • For story, sub-tasks
  • For Bugs, Story Bugs (custom field)

 

Let's say I have a story in Backlog and I have created two bugs and linked them with this story. The automation rule is that all of my bugs moved to In Progress only then the Story will be moved. Here is the screenshot of the automation rule. 
Linked Issues To-Do - In Prog.png

So when I these bugs from backlog to In Progress, My story moves to In Progress but I get an error every time. Attaching the error. 

Linked Issue Error..png

Please let me know what I am doing wrong here. Thanks.
@Trudy Claspill 

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 5, 2023

What was the status of issues DO-104 and DP-103 at the time this rule ran?

Show us the workflow diagram for those types of issues.

Does it include a transition from the status those issues were in to "In Progress"?

Have you tried changing the Transition Issue action to explicitly set the status to In Progress rather than using the Copy option?

Hizkeel Khan
Contributor
October 8, 2023

When I moved these issues from Backlog to In Progress only then the story will move. I do not get these errors all the time but more frequently. I was experimenting, I moved one story bug then took some time and moved another one then the rule ran successfully. 

Anyways, here the screenshots of the workflows. 

 

Workflow for Story
Workflow for Story, Sub-task and Bug.png

Workflow for Story Bug and Sub-task Bug 

Workflow for Story Bug and Sub task bug.png
The workflows are more or less the same so that shouldn't be an issue I think. 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 9, 2023

In the specific example you provided:

What were the statuses of DP-104 and DP-103 at the time the rule ran?

In your workflows it is valid to transition an issue from Backlog to In Progress, but not from any other status to In Progress.

If the issues were not in the Backlog status at the time the rule ran and the rule tried to set them to In Progress, that might explain the error.

I would advise you to add another condition within your For branch to check that the linked issues (the ones found be the For branch, not the ones that are part of the "No linked issues match" condition) are currently in the Backlog status. If they aren't then the step to Transition the issues is going to fail, based on your workflow diagrams.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events