Camms.Incident | May
Welcome to the Known Issues page for the Q2 Feature Release for Camms.Incident. Here, you will find a list of issues that we are currently aware of and working to resolve. Issues will be prioritised based on the Urgency and Impact to our customers. We are committed to addressing them as quickly as possible, with regular updates made to this page for your visibility. We appreciate your patience and understanding as we work to deliver the best possible solution for you. If you encounter any additional issues, please don't hesitate to report them to us through our Camms Support Email (support@cammsgroup.com) or Freshdesk.
ID | Description | Type | Status | Alternative Solution |
1 | Previously submitted signoff authorities shown for approval after again submitting for signoff after rejection | S2 | In QA | Â |
2 | Priority and Severity field values are not hidden conditionally in the Incident Register and MQU | S2 | Open | Â |
3 | Values dropdown is empty for fields with the list name not defined but fetches values based on field name equal list name when defining mandatory and non-mandatory conditions | S3 | Issue Fixing | Â |
4 | Incident Signoff Delegated Approver cannot approve as himself or herself if he or she is added as a Signoff Authority to approve | S3 | In QA | Â |
5 | Archived Records are shown in My Approvals Bubble in My Quick Update | S3 | Open | Â |