How to Configure Issue Tracker Settings

Settings → Issue Tracker is where the tracker’s tenant-wide configuration lives. This article covers two of its tabs: General, which sets what a new issue starts as, and Copy Issue Summary, which controls what a copied issue summary contains and in what order.

Getting there

Open Settings and pick Issue Tracker from the sidebar. It is listed under the MODULES group heading — that heading is a collapse toggle for the group, not a page of its own, so there is nothing to click through on the way.

The page has six tabs, always all six:

General · Statuses · Types · Priorities · Labels · Copy Issue Summary

You land on General. Statuses, Types, Priorities and Labels are the tracker’s four tenant-owned vocabularies, and they are tabs on this screen — not a separate settings page. Board layouts are not configured here at all; they are created and edited from the layout picker on the issue board itself.

If the Issue Tracker module isn’t turned on for your tenant, this section won’t appear in the settings sidebar or in the command palette (Cmd-K, or Ctrl-K on Windows).

General: default type and priority

The General tab, under the New issues heading, sets two things:

• Default type — “What a new issue is filed as when whoever creates it does not choose.”
• Default priority — “The priority a new issue starts on, before the team triages it.”

Both pickers list your workspace’s own rows, so a tenant that renamed or added a type or priority picks from its own words.

Where these defaults actually apply

There are three ways an issue gets created, and the two defaults do not reach all three the same way.

• The tracker’s own New issue sheet — Yes — Yes
• The in-app issue reporter (Settings → Issues) — No — the form always sends a type — Only if the form names none
• The public API (POST /api/v1/issues) — No — an omitted type files the issue untyped — Yes, when priority is omitted

Two points worth spelling out, because they surprise people:

• The reporter form does not read this tab. It pre-selects the first type in your Types order and the middle of your priority ladder, and it always sends a type. Set the tracker’s default type expecting the reporter to follow it and it will not.
• On the public API, omitting type is not the same as saying nothing. The API deliberately turns an omitted type into an explicit “untyped” issue rather than applying the tenant default — an intentional contract, so an existing integration’s behaviour does not change when someone sets a default. If you want the tenant default on an API-created issue, you cannot get it; name the type you want in the request.

The default priority behaves the way you would expect on all three paths: whenever the create names no priority, the tenant default is used.

What happens before you set anything

Nothing is blocked. If your tenant has never opened this page, there is no settings row, and:

• The type falls back to the tracker’s built-in default, bug.
• The priority falls back to the middle of your own priority ladder — not to a built-in “Medium”. A workspace whose least urgent priority is “Whenever” should not have every untriaged issue land there, so the fallback counts your ladder and picks its midpoint.

The same middle-of-the-ladder fallback kicks in if your configured default priority names a priority you have since deleted. If your configured default type no longer exists, the issue is filed untyped rather than filed as something you did not choose.

Reading these settings is best-effort: if the read fails, the create still goes through on the fallbacks above. Configuration never prevents an issue from being filed.

Copy Issue Summary: choosing and ordering sections

The Copy Issue Summary tab controls what’s included when someone copies a summary of an issue, and in what order those pieces appear. The tab’s own note says it plainly: “Copying an issue summary puts the sections below on the clipboard, in this order. Drag to reorder, and clear a checkbox to leave a section out.”

The eight sections, in the order a tenant starts from:

• Header — Number, title, type, status, priority, assignee, reporter, dates and the link.
• Triage — Module, built, scope, reach, customer priority and the flags.
• Description — The issue description as it was written.
• Labels — The free-form labels on the issue.
• Comments — The comments the team left on the issue.
• Conversations — Every linked conversation, with all of its messages in order.
• Attachments — The files and screenshots on the issue.
• External reference — The external reference link.

Each row in the list has:

• A drag handle to reorder it relative to the others.
• A checkbox to include or leave out that section.

Drag a section up or down to change where it lands in the copied summary. Clear a section’s checkbox to leave it out of the copy entirely.

Turning a section back on returns it to where you left it. The order and the on/off state are stored as two separate lists, so switching a section off doesn’t lose its position — re-enable it later and it reappears where you had it, not at the bottom.

Clear every checkbox and the tab warns you: “Every section is off, so a copied summary would be empty.”

If a new section is ever added to the product after your tenant has already configured this tab, it appears at the end of the list and starts unchecked — you opt into it rather than have it silently start appearing in copied summaries.

Permissions

Both tabs are visible to anyone with issues.view, which is also what puts Issue Tracker in the settings sidebar. For that permission the controls are read-only: you can see the current defaults and the current section list and order, but the type and priority pickers, the checkboxes and the drag handles are all disabled.

To change anything on either tab you need issues.manage (workspace owners and superadmins are covered too). The server enforces the same split: reading the settings takes issues.view, writing them takes issues.manage.

Related

• How to report an issue from a conversation — the reporter surface, which does not use the default type and priority set here.
• What are agent stacks
• Handover to humans