TICKET
Documentation
TICKET
With TICKET you manage small cases, tasks, and inquiries that don't belong in a contract:
- Repairs
- Internal tasks
- Support / maintenance cases
- Reports from the team
Tickets have a status, a priority, an assignee, comments, and an audit trail.
- Create a ticket
- Assign a ticket to a colleague
- Set status (e.g., "open" → "in progress" → "done")
- Write comments
- Filter tickets by status
1) Open the ticket list
- Open Tickets in the menu (
/tickets). - Optionally filter by status (
/tickets?status=...).
2) New ticket
- Click "New" (
/tickets/new). - Required field: title.
- Optional: description, status, priority, assignee.
- Save (
POST /tickets/save).
3) Edit ticket
- Open the ticket (
/tickets/{id}). - Click "Edit" (
/tickets/{id}/edit). - Save changes.
4) Change status quickly
- On the detail or list page, choose the status →
POST /tickets/{id}/status.
5) Add a comment
- Open the detail page.
- Enter text in the comment area → save (
POST /tickets/{id}/comments). - Delete a comment via
POST /tickets/{id}/comments/{commentId}/delete.
6) Delete a ticket
POST /tickets/{id}/delete(soft delete).
Status values (/settings/admin/tickets/statuses)
Here you configure which statuses exist (e.g., OFFEN, IN_ARBEIT, WARTET, ERLEDIGT).
- Create / rename a status →
POST /settings/admin/tickets/statuses/save - Delete a status →
POST /settings/admin/tickets/statuses/{key}/delete
Priorities (/settings/admin/tickets/priorities)
Same for priorities (e.g., low, normal, high, urgent).
POST /settings/admin/tickets/priorities/savePOST /settings/admin/tickets/priorities/{key}/delete
Mail settings (/settings/admin/tickets/mail)
If the MAIL plugin is active, you can configure:
- whether a notification is sent on new tickets / status changes
- to whom (assignee, creator, fixed distribution list)
- saved with
POST /settings/admin/tickets/mail/save
"I can't create tickets"
- The
ticket.tickets.createpermission is missing. Enable it in the ROLLEN plugin.
"Status / priority is missing"
- Create it in the admin area (
/settings/admin/tickets/...).
"No email arrives"
- MAIL must be active.
- Check ticket mail settings under
/settings/admin/tickets/mail. - Check the mail queue.
"I don't see other colleagues' tickets"
- Check the
ticket.tickets.viewpermission. - A filter may be active (e.g., "only mine").
User area (/tickets):
GET /tickets— list (filter?status=...)GET /tickets/new— new ticketPOST /tickets/save— create / saveGET /tickets/{id}— detailGET /tickets/{id}/edit— editPOST /tickets/{id}/status— set statusPOST /tickets/{id}/delete— deletePOST /tickets/{id}/comments— add commentPOST /tickets/{id}/comments/{commentId}/delete— delete comment
Admin (/settings/admin/tickets):
GET /settings/admin/tickets/statusesPOST /settings/admin/tickets/statuses/savePOST /settings/admin/tickets/statuses/{key}/deleteGET /settings/admin/tickets/prioritiesPOST /settings/admin/tickets/priorities/savePOST /settings/admin/tickets/priorities/{key}/deleteGET /settings/admin/tickets/mailPOST /settings/admin/tickets/mail/save
ticket.tickets.view— see list/detailticket.tickets.create— create new ticketsticket.tickets.edit— edit tickets / set statusticket.tickets.delete— delete a ticketticket.comments.create— write commentsticket.comments.delete— delete comments
- Status changes and important changes are stored in the ticket audit. On the ticket you can see who did what and when.
- Ticket statuses / priorities are freely definable — only create as many as needed, otherwise the list becomes confusing.
- Short IDs: UUIDs are shown in lists and detail views in short form (e.g. #123e4567). The full UUID is available in the tooltip (on mobile devices by tapping) and can be copied with the copy button next to the short form. Links and URLs continue to use the full UUID.