Change Tasks

[Mego919]

Are Change Tasks the most appropriate way to manage all efforts related to an overall release? Currently, we have separate change requests for these efforts, but it does not allow for all to easily be associated to the overall effort. 

In addition, if Change Tasks are leveraged, do they automatically assume the risk of the overall change request or is there a way to add a Risk Assessment to each task?

[Sandeep Rajput]

@Mego919 You should connect the different changes requests which are part of the release via a parent child relation ship. It can be done via setting the parent field on the change_request record. This way you will be able to leverage Risk Assessment on individual change request.

[Dr Atul G- LNG]

Hi @Mego919 

Greetings!!

Risk assessment has been done on change level not at change task level. In your case strong recommendation is to user change request field in every change task to build relationship and overall end to end tracking possible.

[Mego919]

Thank you! In the past, we had our environment set up so that the tasks inherit the risk level from the parent ticket. Have you ever seen risk assessments added to tasks, rather than inheriting the risk level from the parent?

Is the change task structure best practice?

[Dr Atul G- LNG]

HI @Mego919 

No, I saw a case where task inherit the risk level from the parent bcz the task is not meant for the same. A task is meant to do a specific action. Like If a change has a High Risk but the task is just to reboot the machine then the risk cant be high for this task.

As per best practice, the task inherits CI / plan start /end ( but editable) and follows the full steps of execution ( task respective only)