Tickets

A ticket turns “the display stand is flickering” into a task with responsibility, history and a conversation. Four types: Defect, Maintenance, Check, Other.

Reporting a ticket

1. On an item’s detail page: “Report issue”. Or on the Tickets page: “New ticket” — there you pick the item via search.

2. Title and type are enough; description, priority and due date are optional. The assignment is prefilled with the chosen type’s default and can be changed — a ticket is never unassigned. For a defect, a checkbox sets the item to “Defective” right away.

   Or you simply speak the report: “Fill by voice” at the top of the form records your description (“In the workshop, a rung on the ladder is loose — dangerous”) and suggests title, description, priority, the matching item and even your organization’s custom ticket fields from it — a spoken inventory number finds the item directly. Suggestions are marked with a sparkle icon — you review and adjust; nothing is created until “New ticket”. Something wrong? Just speak the correction: “Correct by voice” (“No, room 501, and priority high”) revises the draft instead of starting over — fields you changed by hand stay untouched.

3. Submit — the responsible person or team is notified.

Reports come in without an account too: whoever scans an item’s QR label can report an issue directly — it appears as a ticket “Via label”.

The ticket overview

Four filter rows above the table narrow things down with one click: Scope (All · Mine — reported by you or assigned to you — · My team; anyone who is in a team lands on “My team” by default), Status (default “Active” = Open and In progress), Type (with “All types” to reset) and Due date (Overdue, Next 7 days, Next 30 days or a custom range). Priority and assignment are filtered directly via the filter icon in the respective column header — active filters appear as removable chips above the table. Clicking a row opens the preview; the title leads to the full ticket page.

Working through

• Status: Open → In progress → Done (or “Won’t fix”). When closing a defect ticket, the app offers to set the item back to “Ready to use”.
• Assignment: to a person or a whole team (e.g. “Facility management” — all team members see the ticket under “My team”).
• Due date: optional, changeable at any time. Overdue tickets appear in red in the table and at the top of “My tasks”; the assigned person is notified once when it passes.
• Checklist: check items to tick off, with photo proof where needed — the foundation for maintenance plans.
• Comments: the conversation on the ticket, with @-mentions — dictated via the microphone button if you like; you can adjust the transcribed text before sending.

Settings

Where new reports land — the organization’s default responsible person, per-ticket-type overrides, team visibility — is explained on My tasks for every area: tickets and orders share the same assignment chain, while maintenance plans, stocktaking and min. stock have their own rules on top. Per ticket type, Settings → Ticket settings additionally lets you define custom fields, say “RMA number” for defects.

Tip

You don’t have to create maintenance-type tickets by hand — maintenance plans generate them automatically at the right time.