I request the ability to set mandatory requirements for Fields using conditions, much like how conditions are are used to trigger Rules.
There are a few reasons why I would like to have this ability:
We've found out that having any field within the Resilient system with a requirement of "Mandatory" or "On-Close" will be required across all tickets, even if the fields are not specified in any New Incident Wizard creation or any tabs whatsoever.
For example, I can create a field call "Test" make it mandatory, not place it the new incident wizard, any tabs, any tasks, workflows, rules etc, but yet it will be required in order to create any incident on the system; the same holds true for with a requirement of "On-Close". We rely heavily on our email connector and if someone where to accidentally create a random test field, make it mandatory, this would halt the functionality of auto-incident generation because of a random mandatory field.
Currently Fields can be visible/hidden based on type using "Sections", but we cannot mandate their completion if they are not always visible. As the user wont have the ability to fill in a Field that they cant see/isnt presented to them.
We would like to have the capability to have fields set as "mandatory" or "optional" per ticket (incident) type. This would increase efficiency and compliance as for example, auditors require all Use Case Design fields to be completed. If any field is not applicable, it still requires a "not applicable" or other similar text in it.
This would allow the ability for different Playbooks used, Groups assigned or Tasks completed to dictate whether a Field must be answered.
Field: "Malware Family"
Required: When Incident Type Contains Malware AND Owner is Level 1
When Required: On-Close
The above example would make the Field "Malware Family" required to be filled in for an incident to be closed when it is a Malware Incident and is Owned by the Level 1 Group.