change implementation and post implementation tasks

[LadySGRho89]

In our change module, if someone implements a change and go to the review state, the implementation and post implementation tasks are cancelled and are not mandatory. Is this standard practice? Should these 2 tasks be required to be completed if there is only one person working on the change? If they are required, why does the tool automatically cancel them?

[Ratnakar7 · Accepted solution]

Hi @LadySGRho89 ,

It is standard practice to require implementation and post-implementation tasks to be completed for a change, regardless of the number of people working on it. These tasks are important to ensure that the change is implemented correctly and that any issues that arise are promptly addressed.

It is possible that the tool automatically cancels these tasks if the change is marked as "successful" in the review state. However, it is important to verify the configuration and settings in your specific instance to ensure that this behavior is expected and intentional.

If you believe that these tasks should not be cancelled and should remain mandatory, you may need to modify the change process and update the configuration in your instance accordingly.

If my response was helpful in resolving the issue, please consider accepting it as a solution by clicking on the ✅Accept solution button and giving it a thumbs up 👍. This will benefit others who may have a similar question in the future.

Thank you!

Ratnakar

[LadySGRho89]

Thank you again for your response. I have on other question. What happens to a change that is on hold once it reaches its planned end date? Would it be considered past due? Also, how long can a change stay on hold?