BACKLOG0
No issues
TRIAGE0
No issues
TO DO0
No issues
IN PROGRESS0
No issues
IN REVIEW0
No issues
DONE0
No issues
FISSUE-1

Issue Title

Status
Issue
Assignee
Due Date
Project
Board Guide

This board uses Agile methodology to organize work. Items move from left to right as they progress through stages.

Board Columns

Backlog

Work that has been identified but not yet started. Items here are waiting to be picked up.

Triage

Newly created items that need to be reviewed, prioritized, and assigned before work begins.

To Do

Prioritized work that is ready to be picked up in the current sprint or cycle.

In Progress

Work that is actively being worked on. Limit items here to stay focused.

Done

Completed work that has been reviewed and accepted.

Work Item Types

T Task

A small, well-defined piece of work that contributes to completing a story or feature.

Example: Write unit tests, update documentation, fix a specific UI component.
B Bug

A defect in the software that causes it to behave unexpectedly or incorrectly.

Example: A button doesn't respond when clicked, or data is saved incorrectly.
F Feature

A distinct functionality or capability delivered to the user, often made up of multiple stories.

Example: User login system, search functionality, or notifications.
S Story

A short description of a feature from the end user's perspective. Typically follows: As a [user], I want [goal] so that [reason].

Example: As a customer, I want to reset my password so I can access my account if I forget it.
E Epic

A large body of work that can be broken down into multiple smaller stories or features. Epics often span multiple sprints.

Example: Build an e-commerce platform — includes search, cart, checkout, and payments.
I Improvement

An enhancement to existing functionality that makes it better, faster, or easier to use.

Example: Improve page load time, add keyboard shortcuts, or simplify a workflow.
C Chore

Work that doesn't directly deliver user value but is necessary for maintenance and infrastructure.

Example: Update dependencies, configure CI/CD, refactor code, or rotate API keys.

Priority Levels

▲▲ Urgent

Requires immediate attention. Blocking other work or affecting users in production.

High

Important work that should be addressed in the current sprint or cycle.

Medium

Standard priority. Should be completed but won't block other work.

Low

Nice to have. Can be deferred if higher-priority work needs attention.

Card Indicators

Subtasks

This item has been broken down into smaller subtasks. The count shows progress.

Dispatched

This item has been dispatched to an AI agent for autonomous execution.

Assigned

This item has been assigned to a team member or agent.