Destination status could not be resolved error is shown - but Status gets updated

Ramya Srinivas September 8, 2024

I get the below Error but the Status does get updated correctly when creating a sub-task.

 

 

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):

1 answer

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 9, 2024

Hi Ramya,

I suspect it is just a timing thing or maybe that there is something else that still triggers it. You might want to put a Re-fetch action prior to the action to transition so it has time to process what is going on. 

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