# Working with tickets

Tickets are the individual work items in a project — tasks, requests, or to-dos. Each
ticket has a status and can be assigned and commented on.

## Create a ticket

1. Open a project and choose **New ticket**. The form fills the whole screen: title and description on the left, assignment, fields, tags and attachments on the right. The same form opens for editing via the pencil on a ticket.
2. Enter a title and a description. Screenshots and other images (PNG, JPEG, GIF or WebP, up to 10 MB) go straight into the text by pasting or dragging them in; the same works in comments. Clicking an image shows it large, Escape closes it. Other files, and images that are too large, belong in the attachments; the editor puts them there and tells you.
3. Optionally assign the ticket to someone and set a status.
4. **Save** closes the form and shows the ticket. **Cancel** or Escape close it without saving; if you have already typed something, Lalabase asks first.

## Status and assignment

Tickets move through statuses (e.g. *open*, *in progress*, *done*). Whoever is assigned a
ticket or created it is automatically notified about changes.

<div class="docs-callout docs-callout--tip">
  <div class="docs-callout__title">Tip</div>
  <p>You can change the status right when commenting — documenting progress and a status change in one step.</p>
</div>

Status and priority are just the default fields — per project you can add any number of
custom fields with your own options (see
[Custom fields & tags](https://lalabase.com/docs/en/guides/ticket-views/custom-fields-tags)).

## The ticket view

An open ticket shows the title and metadata at the top, then the description and files,
then the **history**. You attach files right here without opening the form: via
**Attach file** in the file row. Moving, deleting and the display settings live in the
**"…" menu** at the top right.

By default the history shows **comments only**. The word next to "History" names what is
currently visible; clicking it opens the selection where comments, changes, time entries
and sub-tasks can be toggled individually. The closing line of the history names who
created the ticket and when.

If AI is enabled for your organisation, the **Create summary** action sits next to
"History": it condenses the description and comments into a compact overview that appears
with its date at the top of the history and can be **regenerated** there at any time. A
longer summary starts as a preview of its first few lines; **Show full summary** opens
the rest.

## Comments and mentions

Discuss right on the ticket. Mention someone with `@` and they get a notification — even if
they aren't assigned to the ticket.

## Filtering and finding

Use **+ Filter** above the list to narrow tickets by status, assignment, or other criteria.
Save common views and bring them back as **tabs** above the list.

## What's next

Go deeper with [assigning & changing status](https://lalabase.com/docs/en/guides/ticket-views/assign-status) and switching
between the [board and table views](https://lalabase.com/docs/en/guides/ticket-views/configure-view).