Improve service visualization status when additional rules and propagation rules are used

Improve service visualization status when additional rules and propagation rules are used.

A service named Main service is created with two child services: IPv4 and IPv6.

IPv4 service has a problem tag associated to it. In addition, there is one propagation rule forcing the problem to have Average severity, regardless if original trigger has any other severity.

IPv6 service has a problem tag associated to it. In addition, there is one propagation rule forcing the problem to have Average severity, regardless if original trigger has any other severity.

Since Main service has an additional rule as below, Main service status will be changed from Average to Disaster.
 

 

I would like to suggest adding information regarding propagation rule status when a service severity is changed, as below. This way, user knows the reason why the Main service status is Disaster when actually both child services have original severities High.