Idea ID: 1651919

Relate more than one Busienss Service to a record (Incident, Change & Problem)

Status : Waiting for Votes
Waiting for Votes
See status update history
over 3 years ago

Currently we are using Service Anywhere, one issue that I'm hearing from a number of our users is that they need to link more than one Business Service to a Record. So if you are creating a problem record there could be a number of Business Services affected not just one.

As all changes, incidents etc must have a service related to it, is there a reason for why only one can be linked or is this something that has now been rectified within SMAX compared to SAW?


  • In the incident, we should at least have the list of affected services based on the involved CIs just like we have in a Change record.

  • Hello.. this is really essential for the customer I work, where the incident prioritization and SLA must be defined based on affected services (with highest business criticality)


  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.

     this has not been changed in SMAX, so Ikeeping this open for votes