Jira Backlog
What it is
The Jira Backlog is a Jira-style work item system embedded inside every board. It allows PMs to generate, edit, and review a structured backlog without leaving the board context.
Work items and sticky notes coexist on the same board — notes capture thinking and research; work items capture the deliverable scope.
Accessing the backlog
Click the Jira Backlog tab in the left sidebar. The tab shows:
- A table of all work items
- The AI generation action bar at the top
- A context panel showing sticky notes for AI generation reference
Work item structure
| Field | Description |
|---|---|
| Key | Sequential identifier (e.g. EPIC-001, STORY-003) |
| Type | idea, discovery, prototype, epic, story, task, subtask, or bug |
| Summary | One-line title |
| Description | Detailed Markdown body |
| Status | todo, in_progress, in_review, done, or cancelled |
| Priority | highest, high, medium, low, or lowest |
| Parent | Hierarchy link (epics contain stories; stories contain tasks) |
| Acceptance criteria | Checklist items (can be marked complete) |
| No-gos | Explicit out-of-scope constraints |
| Dependencies | Links to blocking or blocked-by items |
| Source notes | Links back to the sticky notes this item was derived from |
AI generation workflow
Work item generation follows a multi-step hierarchy:
| Step | Types generated |
|---|---|
| 1 | Ideas |
| 2 | Discoveries |
| 3 | Prototypes |
| 4 | Epics and Stories |
| 5 | Tasks and Subtasks |
Click Generate [next step] in the Jira Action Bar to generate the next missing tier. The AI uses your sticky notes as context.
You can also:
- Regenerate selected items — improve specific items by selecting them and clicking Regenerate.
- Generate children — decompose a selected parent item into child items.
Editing work items
Click any work item row to open it in the full-screen Work Item Editor — a TipTap WYSIWYG editor with:
- Structured sections (Description, Acceptance Criteria, No-gos)
- Inline AI suggestions via
@subagentannotation buttons - Text selection toolbar for field-level AI rewrite
Changes are debounced (800ms) and flushed on editor close — so edits don't generate a network request on every keystroke.
Inline AI review
Click Review Project in the Jira Action Bar to run AI analysis across all work items and sticky notes simultaneously. The AI:
- Identifies gaps, inconsistencies, or missing acceptance criteria
- Injects inline suggestions as
@subagentblockquotes in the work item editor - Each suggestion has action buttons to accept, rewrite, or dismiss
Syncing work items
Work items are synced to D1 via the same push pipeline as notes. They are included in the jiraItems field of the sync payload. Soft deletes use deletedAt timestamps.
Hierarchy and key format
| Type | Key prefix | Example |
|---|---|---|
| Idea | IDEA | IDEA-001 |
| Discovery | DISC | DISC-001 |
| Prototype | PROTO | PROTO-001 |
| Epic | EPIC | EPIC-001 |
| Story | STORY | STORY-001 |
| Task | TASK | TASK-001 |
| Subtask | SUB | SUB-001 |
| Bug | BUG | BUG-001 |
Keys are assigned sequentially per type within a board. Deleted items' keys are not reused.
See also
- Jira AI — AI generation, analyze, and rewrite details
- Editor and Sidebar — Jira Backlog tab in the sidebar
- Sync Engine — How work items sync to D1