Feature Requests

Display the Fault Type and Request Description on separate lines for better readability. The Fault Type and Request Description are currently displayed together on the same line in the request list. This causes the information to appear truncated and difficult to read, especially when the description is longer. [ALR]

Currently, due dates can only be configured relative to the request creation date/time. This may not be suitable for request types that are tied to a future event or scheduled activity. [CPF]

Currently, the file upload limit for video responses and multi image/video response fields is capped at 10MB, which is too restrictive for practical fault reporting use cases. For example, a short 1080p video can already exceed 15MB. This prevents users from uploading important diagnostic videos needed to properly capture machine faults, especially for long production lines or large equipment. [OJJ Foods]

Allow requestors to save requests as a draft before submitting, similar to the existing logic in Checklists. Currently, when creating requests, any entered information is lost if the user leaves the page before submitting. This can happen when engineers are interrupted by alarms or other urgent tasks. A Save as Draft option would allow users to preserve partially completed requests and return to submit them later. [Princeton DG]

Client would like to include details from other asset fields in the PDF report. Also, current asset details don't include location details, serial no etc. [KWSH]

To include an option for manager to set signature mandatory for requests. [KWSH]

The option to hide the status table from the PDF report. Displaying this table in the PDF may expose internal workflows that clients do not need requestors have visibility into. Hiding it allows the PDF to be used as a cleaner client-facing service report. [KWSH]

Allow the scroll bar between the service request list and preview panel to be dragged sideways to widen either of the two panels. Also, to allow multiple columns for questions/response fields

Currently, the system categorizes requests sent via email based on its "content". The client wishes to prevent requests to be categorized into a certain service request form they created. Either by: A) Being able to disable the service request form from being selected when submitting a request via email or B) When submitting a service request via email, the requestor can select from the list of service request forms created to which the email will be categorized

Is it possible to assign this per department, or have it automatically categorized based on the responses in the form such as using single-choice or multiple-choice answers? The idea is that whenever someone submits a request, it will automatically be tagged based on the corresponding department on our Inventory request system. Thank you