Best practices for JSM dependent services

[YY Brother]

Hi,

Has anyone practiced this automation in your work? Is it useful?

Services

If a change to one service potentially impacts your other services, you can create a service relationship. You can then use this service relationship and automation rules to flag changes that could impact a critical service, before those changes go live.

Thanks,

YY Brother

[Cristian0791]

Hi YY,

In some cases you may have a form for a System change of one Application. Let call this Application A. 

A change to Application A (that is a core Application may trigger changes to other application as B,C,D)

The use case is the following:

1.A Customer will raise a change in App A.

2.An Agent will evaluate the change and if the change will "Impact Other System/s" (dropdown field Yes and No)

3.Automation will be created( When the Dropdown field "Other System/s" is change to yes, An email will be send to each Other Systems stakeholders to check if this change is or is not affecting their system.

[YY Brother]

Hi  @Cristian0791 

Thanks for sharing your experience.

If we've built the dependencies between services (JSM Assets), I think once the Change requester choose a service, we can get all the services which are dependent by the chosen service directly. So maybe we don't need the requester to choose if any other service will be impacted or not. What do you think of it？

[Cristian0791]

If you have a mapping matrix of system this should be ok and you will not need a dropdown field. It should work. You may test it in a demo enviroment / project.

[YY Brother]

What feature I’m expecting is:

When App A depends on App B,

and App B has open incidents currently,

then I should be notified in the Production Change Request ticket detail view of App A that there’s a potentially impacted incident from the dependent Services of App B.