Idea ID 2775190
To meet business requirement and have the information detail, CI information and relationship is important, ensuring the relationship added to the ticket is essential.
Rule set to make association field like involved CI or involved Device is mandatory, this help to ensure correct information available in the ticket.
When a user raise a change request for an issues, it is essential to know which CI is the issues impacting on or related to, if the user didn't include the involved CI, time will be waste for communication and ticket stuck in pending due to missing information.
To ensure user include the involved CI, (OOB is an association field many2many) ruleset to make the field deviceAffectedByChange field mandatory.
The step is that there is no ruleset which allow to set association field to be mandatory, as per attached screenshot the option to select any association field (e.g. DeviceAffectedByChange) is not available.
All reference is OOB field and OOB ruleset.
information user via email or other communication system(phone call, messaging) to highlight user about the missing information. Or using the discussion function of the ticket to highlight the missing information.
User felt the limitation of Microfocus SMAX product and value of SMAX is reduce. Time is wasted to do the verification manually.
RuleSet: Allow setting association field mandatory in "after change" phase.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.