If the ticket has been assigned to a user, this contains the assigner and assignee user IDs.
The assigner is the person who assigned the ticket. The assignee is the person who will call the ticket for service.
{ "assigner": 1459, "assignee": 1460 }
If the person has assigned a ticket to themselves, the assigner and assignee will be equal.
{ "assigner": 1459, "assignee": 1459 }
If the ticket has been called, then this object contains the time the ticket was called, in ISO8601 format, with milliseconds.
{ "date": "2017-10-31T17:30:00.000Z" }
If the ticket has been cancelled, this contains the time the ticket was cancelled, in ISO8601 format, and the ID of the User who cancelled the ticket.
{ "date": "2017-10-31T17:30:00.000Z", "canceller": 1445 }
An object that contains the creation timestamp of the ticket in ISO8601 format, with milliseconds.
{ "date": "2017-10-31T17:30:00.000Z" }
The e-mail address of the visitor. For example: "jsmith224@example.com"
List of custom fields and their values attached to the ticket.
The first name of the visitor. For example, "Jane".
This ticket's unique ID. For example, 14995020
List of interactions of this ticket.
List of the ticket's labels.
The last name of the visitor. For example, "Smith".
The ID of the line that this ticket belongs to. All tickets belong to a line. For example, 14142.
List of SMS messages exchanged with this visitor.
If the ticket has been reordered, this will contain an ISO8601 timestamp with milliseconds that should be preferred over the "created date" to sort tickets by.
"orderAfter": "2017-10-31T17:30:00.000Z"
To sort tickets chronologically, taking into account reordering, the orderAfter date should be preferred before the created date:
const tickets = [ ... ]; tickets.sort((ticketA, ticketB) => { const timeA = ticketA.orderAfter || ticketA.created.date; const timeB = ticketB.orderAfter || ticketB.created.date; return new Date(timeA) - new Date(timeB); });
The phone number of the visitor. For example: 3725551111
If the ticket has been marked served, then this object contains the time the ticket was served, in ISO8601 format, with milliseconds.
Describes how the visitor was added into the queue.
PHONE - The visitor used the discontinued Qminder Remote Queuing app.
MANUAL - The visitor was added into the queue by a clerk.
NAME - The visitor added themselves into a queue via iPad Sign-In (a Name Device).
PRINTER - The visitor used a printer (discontinued) to queue up.
The current status of this ticket.
Generated using TypeDoc
Represents a person in the queue. Every time someone is added to the queue, a ticket is created in Qminder. The ticket contains the person's name, phone number, email address or other custom fields.
Tickets belong to lines. Tickets can have many TicketExtras.
If the location has SMS enabled, some visitors may exchange messages with the location. Those messages are stored with the ticket in the TicketMessages list.
Methods that work with Tickets can be found under {@link TicketService}, or
Qminder.tickets.For example:
To create a Ticket, call {@link TicketService.create}. To search for tickets, call {@link TicketService.search}.