The change ticket moved to New status after approval

[Deepa12]

we recently migrated dev environment to sandiego upgrade, stil production we didnt do.

we faced the issue that the change ticket moved to New status after approval.

For both approvals i did, clicked on the update button after each approval.  To clarify, when i approves on behalf of others, i approves in list view mode at the bottom of the change request and never leaves the change request form.

For both change requests, i clicked the update button after doing first approval.

For the next/final approval of my change request, i did NOT click the update button after approving.  Instead, i clicked refresh/reload and the state was correctly set to scheduled, otherwise this change moved to new status and history has no evidence of state ever being set to new.

this issue is not happening in production..... could you assist me where to check and fix this issue

[Tony Chatfield1]

Hi, unfortunately your post contains no clear details which would allow the forum to assist with diagnostics and testing in a San Diego instance with the OOB 'normal' change process I do not see the same behavior.

Have you checked the change workflow that ran against the task, is is still running? does the workflow log show any errors or unusual issues.

Have you reviewed any custom workflow, business rules or other script(s) that might have run against the change request as a result of the approval being set to approved (this could be on the change request or approvals table).

Perhaps you could update this thread with clear and specific details of your configuration and process so that the forum can better understand your issue.