Issue statuses, custom fields and automations

Each team, and Personal, has its own statuses, custom fields and automation rules for issues.

Statuses

Statuses in the Issues section of the sidebar shows the workflow in order, with each status's category. A new team starts with these statuses:

Team admins change the workflow:

• Create status adds a status with a name and a category.
• Choose a status's name to rename it or change its category.
• Move up and Move down change the order, which is also the order of the columns on the board and of the status menus.
• Remove removes a status once no issue uses it. Move its issues to another status first. Backlog cannot be removed; new issues start in it.

The category, not the name, decides what a status means. A status in the Completed category counts as completed in projects, milestones and cycles, and records the date the issue was completed; a Cancelled status records the date it was cancelled. The Active quick view shows Started statuses, and Backlog shows Backlog statuses. Changing a status's category updates the completed and cancelled dates of the issues in it.

Custom fields

Members who can edit open More on the Issues page, then Custom fields, and choose Create field. A field has a name and a type: Text, Number, Select, Multi-select, Date, Checkbox or User. For Select and Multi-select, enter one option per line. A User field takes a team member.

Fields appear on the issue page and on the issue's edit page, where they are filled in and saved with Save custom fields. Once a field has a saved value on any issue, its type and options cannot be changed; its name can. Remove takes the field and its values off issue pages and out of exports. CSV and JSON exports include each field and its values.

Automations

Members who can edit open More on the Issues page, then Automations, and choose Create rule. A rule has three parts:

• When: Issue created, Status changed, Label added, Assignee changed, or Public form submitted.
• And the issue is: any issue, or one with a chosen status, priority, label or project.
• Then: set a priority or set a status.

Rules run when the change happens, in the order they are listed. A change made by a rule appears in the issue's activity with the rule's name, and does not start another rule. Pause stops a rule without removing it, and Enable starts it again.

For example, a rule with When Public form submitted and Then Set priority: High gives every report from a public form high priority (see Triage and public issue forms).

For help with statuses, fields or automations, Contact support.