# Tickets

The `tickets` object stores support and service requests. It is extensible but cannot be deleted.

## Standard fields

| Field | Type | Behavior |
|  --- | --- | --- |
| `Name` | string | Required record title. |
| `Description` | string (text) | Detailed issue or request description. |
| `Status` | select | Required ticket status. Defaults to New. |
| `Users` | prismaRelation | Assigned Frontline account users. |
| `Last Status Change` | date | Read-only timestamp updated when Status changes. |


The default Status options are New, On You, On Customer, On Hold, and Closed. These options can be customized for the account.

## Built-in relations

| Relation | Target | Cardinality |
|  --- | --- | --- |
| `People` | `people` | Many-to-many |
| `Company` | `companies` | Many-to-one |


The relations are already defined. Link records with the relation endpoints rather than creating replacement fields.

## Workflow behavior

Tickets use a Kanban view grouped by `Status` by default.

Whenever Status changes, Frontline updates `Last Status Change` automatically. Do not maintain a duplicate timestamp field through a workflow.

## Example

```bash
frontline object record create tickets --data '{
  "Name": "Unable to access dashboard",
  "Description": "The dashboard returns an authorization error.",
  "Status": "New"
}'
```

Inspect the live schema and Status options before writing records:

```bash
frontline object schema tickets
frontline object field list tickets
```