Create issues

Create issues for a team, set properties, and link them to projects and cycles.

File work for a team, or keep it personal.

Overview

Issues are the unit of execution — bugs, features, tasks, and stories.

An issue belongs to a single team, or is Personal. It needs a title. Type is Bug, Feature, Task, or Story. Status, assignee, and the rest can use defaults until you set them. Opened from a team, project, or cycle, the composer pre-fills that context.

Creating issues

  • Use the keyboard shortcut C to open the composer
  • Click New issue on Issues, a project, a cycle, or My Issues
  • Open the command menu with Cmd/Ctrl K and choose Create new issue…
  • To start from a template, choose Create new issue from template… in the command menu, or open the Template picker beside the team selector

You can also create a sub-issue from a parent.

In the composer, set Status, Assignee, Priority, and Labels as needed. Link a Project, Cycle, or Release when the work already has a home. Attach files with Attach files.

Estimate and due date are optional. On a team issue, due date lives in the … menu (Shift D).

Turn on Personal in the composer to create an issue without a team. Personal issues do not use team estimates or cycles. They appear under My Issues. Move them onto a team when the work is shared.

Press Cmd/Ctrl Enter or click Create issue to save. See Issue templates for standard and form templates, including Copy URL to create issue from template.

Drafts

If you leave the composer without creating, Pulse keeps the draft on that client and restores it the next time you press C.

Use Create more to save and start another issue in the same composer. Cmd/Ctrl Shift Enter does the same.

Last updated on