Tickets

Tickets are the smallest unit of work in Tessel. A ticket can hold a bug report, a slice of a feature, a follow-up from a customer call or a chore nobody wants to forget.

Overview

Every ticket belongs to exactly one team and carries a key made of the team's prefix and a running number, such as TSL-412. A ticket needs a title and a state; everything else is optional and can be filled in later.

Creating tickets

• Press N anywhere in the app to open the composer

• Click New ticket in the top left of the sidebar

• To start from a template, press Alt N and pick one from the list

• Visit tessel.new in any browser tab to open a blank composer in your last-used team

The composer remembers the team, state and labels of the last ticket you created, so filing five related tickets in a row takes five titles and nothing else. Toggle Keep open to file several in one sitting.

Paste to create

Paste a list of lines into an empty composer and Tessel offers to turn each line into its own ticket. Indented lines become sub-tickets of the line above them.

Drafts

If you close the composer before saving, the text is kept as a draft. Drafts sync across devices and appear under My drafts in the sidebar until you file or discard them.

Create a ticket by email

Each team has an intake address. Mail sent to it becomes a ticket in that team's intake inbox, with the subject as the title and the body as the description. Attachments up to 25 MB are kept.

Team intake address

Find the address under Team settings → Intake → Email. You can rotate it at any time; the old address stops accepting mail immediately.

Templated intake address

Each ticket template can have its own address. Mail sent there is filed with the template's properties already applied, which is a tidy way to route support escalations straight to the right labels.

Recurring tickets

Some work comes back on a schedule: rotating on-call notes, a monthly dependency audit, quarterly access reviews. Make any ticket recurring and Tessel files a fresh copy on the cadence you choose.

1. Open the ticket composer

2. Apply a template (optional)

3. Open the … menu

4. Choose Repeat…

Recurring tickets are listed under Team settings → Recurring. The next copy is filed at 00:01 on its due date, in the team's time zone.

Convert an existing ticket

Open the ticket, choose … → Repeat…, then pick the first due date and the cadence. You can also press Cmd K and type repeat.

Create from team settings

1. Go to Team settings → Recurring

2. Click New and choose the schedule

Prefilled ticket links

A link can open the composer with fields already set. Share it in a runbook, a form confirmation or a chat bot.

• https://tessel.app/team/<key>/new

• https://tessel.app/new

• https://tessel.new

To prefill fields:

1. Add a ? to the end of the link

2. Name the field you want to set

3. Add =

4. Add the value, and join further fields with &

Editing tickets

Click any field in the ticket view to change it, or select the ticket and use its shortcut: S for state, P for priority, A for assignee, L for labels. Edits are saved as you make them and recorded in the ticket's history.

Restore an earlier description

Open … → Description history to see every saved version of the description, who wrote it and when. Pick a version and choose Restore; the current text is kept in the history, so restoring is always reversible.

Move a ticket to another team

Press Cmd Shift M, or open … → Move. Moving a ticket gives it a new key in the destination team. The old key keeps working: links and searches that use it redirect to the ticket.

FAQ