The automation is set to transition a parent issue to Selecting MO Tasks if its current status is Waiting for BA Tasks, when the issue’s sub-task is transitioned from Dev Task Assigned to Dev Task Completed.
It was working until I modified fields, screens and workflows. The error mentions a problem with the destination status, but I don’t see a problem with the status name, so I’m guessing there’s a hidden problem such as a screen missing an association.
Automation log error:
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):
TAST6-1025 (Waiting for BA Tasks - 10200)
Relevant piece of automation:
Relevant parent workflow statuses:
Relevant sub-task workflow statuses:
Hello Praveen!
Could you elaborate more on how to reproduce this issue and what exactly happens, maybe taking a screenshot so we can visualise the issue?
From the description, this appears to be either something related to permissions, with the user not having certain permissions to see/edit some fields, or something related to his environment (browser, cache, so on) as you mention this doesn't happen with other users.
With a screenshot of the issue we might be able to understand what is happening and look for a resolution.
Let us know if you have any further questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.