All ideas

Currently when you use a custom form and allow users to select a building, it does not filter the spaces/rooms based on the building that is selected. It should only show spaces that are assigned to the building.

I was looking at the mass update feature since we needed to update the request time a lot of request/work orders and discovered that the request type is not of the options allowed in Mass update. If we had this option here as well that would make ...

We would like for an easy way to clarify which requests are created via the MLS/MLW integration, similar to how you can track whether or not a request is from a PM. A column to link that data with a request ID from ML Schedules may be nice as well.

Currently if a role has the permission to complete a work order on behalf of other they can complete work order even in pending status. We would like all work orders to be approved before anyone assigned can mark complete. Even if the staff themse...

It would be nice to import inventory with csv. This would make it easy when adding a lot of new inventory item so they wouldn't need to be added manually. It would also be convenient when updating inventory.

"This account is managed by Google. You can't change your E-mail Address." - shows when editing a user just with Microsoft/Azure SAML setup, so it is causing confusion because the system is not connected to Google at all.

If you originally created/submitted a Technology request in 'Walkthrough mode', then want to edit it back to a Maintenance request type, the system will not allow edit to occur.

When printing a work order, it currently only records that history if printing "print details." We like to print the "print work form." As of now, when printing the "print work form" it is not marked as printed in the history of the work order. We...

Work orders submitted via email are hard to read because recipients, the subject, and the email body are added to the work order as continuous text without character returns.

I want to propose adding “Ticket Macros” to the system so our techs can execute multi-step standardized workflows in one action. Example use cases: closing a ticket with verification, escalating to Tier 2 with triage context, reopening with struct...