Issue keys, types and epics

Every Grid issue has a short, permanent key built from its project key and a number, such as WEB-142. Keys make issues easy to reference in chat, email and commits, and every way of creating an issue gets one automatically.

Issue keys

• Each project has a key of 2 to 6 letters, unique in your workspace (for example WEB or OPS).
• Issues are numbered in order within the project: WEB-1, WEB-2 and so on.
• Moving an issue to another project gives it a new key from that project.
• Issues without a project use your workspace prefix (GRID by default).
• Keys show on board cards, list rows and the issue header, where you can copy a link.
• Search by key on the board, the list and the link picker.

Deep links

/grid/issue/WEB-142

Issue types

• Task: a piece of work.
• Bug: something broken.
• Story: a user-facing requirement.
• Epic: a large body of work that groups other issues.
• Pick the type in quick add, change it from the issue's type switcher or inline in the list, and filter the board by type.

Epics, subtasks and reporters

• Link an issue to an epic with the epic picker; the epic shows as a chip on the card.
• Subtasks are separate from epics: a subtask belongs to one parent issue.
• The reporter (who created the issue) is recorded automatically and shown in the detail panel.
• The detail panel shows the Project / KEY breadcrumb, created and updated dates and how long the issue has been in its current status.

1. 1Create an Epic for the initiative, for example Checkout redesign.
2. 2Create Stories and Tasks and link each to the epic.
3. 3On the board, choose swimlanes by epic to see progress per initiative.
4. 4Share issue keys in Beam or email so teammates can jump straight to them.