Maintenance Tasks for multiple groups

[Sherry Nickolof]

Our application group wants to add child tasks to a maintenance task which will affect multiple groups. For example, if there is a security vulnerability, they want to open a maintenance task and assign to our server team, security team and applications team. I believe these should go through the change process, by either opening a Standard change or Normal low change. 

How would others address the scenario above?

Is there documentation that defines best practice for using maintenance tasks?

What are others using maintenance tasks for and how are they using them? 

Thank you!

Sherry

[GTSNOW]

Hi, Why dont you create a BR which will create change tasks for all 3 groups for maintenance in once change with a condition that change is created from Vulnerability Remediation Task.

If you found my response helpful or relevant to your query, please consider clicking the "Helpful" button or giving it a "Like". This not only helps others identify useful replies but also encourages contributors like me to continue assisting the community. Thank you for your support!

[Sherry Nickolof]

To clarify, you're suggesting opening a Standard change from the maintenance task "vulnerability remediation" and then a BR to create the change tasks? I'll run that by our SNOW Admins. Thank you!

[GTSNOW · Accepted solution]

Are you referring maintenance task as Vulnerability Remediation?

VG is a Remediation task from where you can create a change. What I am saying to create Change Task to all different teams automatically when change is created from VR. If you have any different thoughts or requirement, please confirm.