Coming soon

Tasks and issues

Every piece of work, tracked exactly the way you need it. Issue types, subtasks, dependencies, comments, and a full activity log on every task.

A detailed issue with fields, comments, and activity.
0A56-51

Copy of Build project overview analytics #48 test

Seeded issue with module, cycle, label, state, and estimate data for analytics testing.

No description provided.

Core
State
In Progress
Priority
High
Assignee
AAchala Rathnayaka
Parent Issue
None
Classification
Labels
Bug Backend
Modules
Planning
Cycle
Sprint 1 - Completed
Planning
Estimate
Select estimate
Start date
May 18, 2026
Due date
May 30, 2026
Time tracking sequence
Time tracking
Actual vs estimate: 0m 0s / 30m 0s
Total
0m 0s
Yours
0m 0s
Active
0m 0s
No time logged yet.

How issue tracking works

Built for the depth your team actually needs.

Four building blocks. Together they cover everything from a one-line task to a multi-team initiative with dependencies, custom data, and a full audit trail.

01 · Issue types

Five built-in types, configurable to match your workflow.

Tasks, Bugs, Stories, Features, and Sub-tasks each ship with their own icon, color, and default fields. Add new types, rename existing ones, or change the default field set per workspace without leaving the settings panel.

  • Task, Bug, Story, Feature, Sub-task built in
  • Per-type icons, colors, and default fields
  • Add custom types per workspace
  • Type-specific create modal
Create issue
Type
BugA defect with steps to reproduce and severity.
TitleShort, descriptive issue title…
Default fields for bug
Title
Severity
Steps to reproduce
Environment
Assignee

02 · Fields and properties

Every detail your team needs, on every issue.

Assignees, priority, start and due dates, labels, and a customisable status pipeline ship on every issue. Configure the defaults per project so each team sees the fields that matter to them.

  • Single or multiple assignees
  • Five-level priority with color coding
  • Start and due dates with planned schedule
  • Status pipeline you define per project
Assigneessingle or multi
AMSCMP+2
Assign one teammate or a whole squad to any issue.
Prioritycolor-coded
Urgent
High
Medium
Low
None
Datesstart and due
Start
May 18
→
Due
Jun 4
Track planned and actual schedule on every issue.
Labelscross-project
BugAuthFeatureUXChore
Tag issues and filter across every project in the workspace.
Statusdefined per project
Backlog
→
Todo
→
In Progress
→
In Review
→
Done
Each project defines its own pipeline, from a simple Todo and Done flow to a multi-stage review process.

03 · Subtasks and dependencies

Break work down. Track what blocks what.

Nest subtasks several levels deep and let progress roll up to the parent automatically. Mark dependencies between issues with "blocked by" and "blocks" relations. Link duplicates, related work, and clones so context follows the work.

  • Subtasks nested several levels deep
  • Automatic progress roll-up to the parent
  • Blocked by and blocks relations
  • Duplicate, relates to, and cloned from links
BugBCN-049In Progress
Refactor authentication middleware
Progress rolls up from 4 subtasks
50% complete2 / 4 done
Subtasks
BCN-051Add token cache with TTLIn Progress
BCN-061Define cache invalidation rulesDone
BCN-062Wire role-change eventsIn Progress
BCN-052Integration tests against staging IdPTodo
BCN-053Document migration stepsDone
Blocked by
BCN-045Provision new staging IdP
Blocks
BCN-068Roll out SSO for enterprise tier
Duplicate ofBCN-039
Relates toBCN-072

04 · Activity and collaboration

Every field change, comment, and decision in one timeline.

Rich text comments with @mentions, emoji reactions, and threaded replies sit on every issue. Drag and drop attachments and paste links to get inline previews. The activity log records every field change with the author and timestamp so nothing slips through.

  • Rich text comments with @mentions and reactions
  • Threaded replies on every comment
  • Drag-and-drop attachments with link previews
  • Full activity log on every issue
Comments 2
SC
Sarah Chen2h ago
Confirmed the regression on staging. Token cache TTL needs to drop to 30s. Pinging @alex to review before we merge.
L
Lena O.1h ago
Same here. The cache invalidation logic looks tight.
Write a comment, attach a file, or @mention a teammate…
Attachments 2
auth-flow-v2.pdf
PDF · 1.2 MB · added by Sarah Chen
Figma · Auth flow v2
figma.com/file/auth-flow
Drag and drop to attach
Activity history 4
Sarah C.changed status from Todo to In Progress2h ago
Marcus P.added label Auth5h ago
Lena O.reassigned to Alex M.8h ago
Alex M.changed estimate from M to L1d ago

Create your first task in under a minute.

Start tracking work with the structure your team actually needs. Free for unlimited members.

No credit card required