Issues

Issues are the unit of execution in Pulse — tasks, bugs, improvements, and small deliverables that move through a team workflow.

When to use an issue

Create an issue when:

• One person (or a pair) can own the work
• The task moves through status columns on a board
• It should appear in a cycle or release
• It belongs to a project or milestone

Use a project for multi-issue deliverables with milestones. Use a request when another team is asking you to consider work.

Team scope

Every issue belongs to a team. The team determines:

• Available workflow statuses
• Labels and priority options
• Estimate scale (if enabled)
• Which cycles and releases can include the issue

Personal issues without a team exist for individual tracking; they do not use team estimates or cycles.

Default workflow

Out of the box, Pulse maps statuses to lifecycle types:

Teams customize statuses under Settings → Your teams → <team> → Issue statuses & automations. Analytics group by status type so custom columns still roll up to Unstarted / Started / Completed.

See Status and workflow.

Relationships

Issues connect to other objects:

• Project and milestone — delivery context
• Cycle — time-boxed iteration
• Release — shipped version
• Parent / sub-issues — break down large work
• Relations — blocked-by, related, duplicate (when enabled)

Views

Open Issues under a team or My issues for personal assignments. Switch layouts:

• List / Table — dense filtering and sorting
• Board — columns by status
• Timeline — schedule-oriented planning

Display options (group, sort, properties shown) persist per view when saved.

Properties

Common fields:

• Assignee and delegate
• Priority — see Priority
• Labels — see Labels
• Estimate — see Estimates
• Due date

Templates

Issue templates pre-fill properties and descriptions — or ask form questions before creation. See Issue templates.

Permissions

Creating issues requires create permission on issues for the team. Moving to certain statuses or editing others' issues may require higher roles depending on workspace policy.

Next