Feature Requests

To include 'Reason' when updating parts in checklists. [OJJ Foods]

Allow managers to export checklist responses linked to requests as a CSV export (for data analysis and reporting) and as a downloadable checklist file directly from the request. When a request has a linked checklist, managers are unable to extract the checklist form responses in a CSV format. Additionally, there is currently no option to download the linked checklist data directly from the request. [OJJ Foods]

Currently the categories in Vendors are fixed and not editable. At the same time, there's no way to create custom categories. [OJJ Foods]

Currently, all custom processing statuses are grouped under "Processing" in the Request Data > KPIs. It would be beneficial to have the ability to break down KPIs by the different custom processing statuses, providing a clearer view of the request response time and allowing managers to track specific stages of the process more effectively. [ebridge]

Preserve and display the original paragraph breaks and line formatting exactly as entered by the user across web, mobile, and PDFs. Although request descriptions can be entered using multiple paragraphs or line breaks, they are currently displayed as a single continuous paragraph. This reduces readability, especially for longer or more detailed descriptions. [Princeton DG]

Allow users to link a customer to a request. When the request status is updated to Complete, the system should automatically email the completed request PDF to the linked customer, similar to the existing Checklist behavior. [Don Jon]

Current Limitation: Currently, Workflows do not support multiple reminder intervals (e.g. 60 minutes, 120 minutes) Proposed Enhancement: Ability to trigger multiple reminders or alerts at configurable time intervals (e.g. after 60 minutes, 120 minutes) [UOL x United Square]

Currently, due dates for requests are typically set by managers or administrators. Responders (e.g. contractors) are unable to define their own timelines for assigned work orders. Proposed Enhancement: Allow responders or contractors to set or update the due date for requests created assigned to or created by them (e.g. as a “Projected Delivery Date”). These due dates should support reminders and notifications, similar to existing due date alerts. Why This Is Helpful: This holds contractors accountable for their own planning and timelines, improves visibility into expected delivery dates, enables more accurate scheduling and follow-ups, and ensures reminders are aligned with contractor-committed deadlines rather than assumed timelines. [CSK Landscape]

To include SOR Table in Custom PDF download. [CSK Landscape]

For certain checklists, the work may span multiple days. In these cases, the current “Require check start time and end time” option is not sufficient, as it only captures time within the same day. It would be more helpful to allow responders to record both start date & time and end date & time. This enhancement would better reflect the actual duration of long-running tasks and provide more accurate tracking for reporting and audit purposes. [Princeton DG]