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

Idea ID 1651919

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

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?

3 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

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.

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

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

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)

 

New Member.

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.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.