Work Items
Work Items turn approved requirements into trackable engineering tasks. Each work item carries a status, assignee, priority, sprint, and optional story-point estimate, so planning and day-to-day execution live in the same place as the requirements they trace back to.
The three scopes
The Work Items entry in the left sidebar opens a hub with three tabs:
| Tab | What it shows | Best for |
|---|---|---|
| My Items | Everything assigned to you, across every project you belong to. | Your personal to-do queue. |
| Project | The active project's board. Switches between three views (below). | Day-to-day delivery. |
| Insights | Burndown, velocity, and sprint progress for the active sprint. | Stand-ups and reviews. |
Open a project from any tab to make the Project tab available.
Three ways to view your project's work
Inside the Project tab, switch between List, Kanban, and Gantt using the toggle in the top-right. Your choice is remembered per project, so each project can have its own default.
List
A filterable, spreadsheet-style view. Inline-edit status, priority, assignee, sprint, estimate, and notes without leaving the row. Use the status pills above the board both as a completion summary and as one-click filters.
Best for triage, bulk updates, and copy-to-AI workflows.
Kanban
Four drag-and-drop columns that match the status lifecycle:
To Do → In Progress → In Review → Done
Drag any card between columns to update its status. The change is saved instantly. Each card shows the requirement ID, title, priority (coloured dot), sprint badge, estimate badge, and assignee initials.
Best for daily stand-ups, work-in-progress visibility, and team-board reviews.
Gantt
A timeline of your sprints. Each bar spans a sprint's start and end date; the fill shows percent complete. The vertical red line marks today. Click any sprint bar to drill straight into that sprint in the List view.
When every item in a sprint has a story-point estimate, the completion percentage switches from item-count to estimate-sum — so velocity-aware teams see the same number as Insights.
Best for release planning and roadmap conversations.
Creating work items
Automatic (recommended)
Accepting an AI-suggested requirement automatically creates a work item for it. This is the standard flywheel:
AI generates requirement suggestion
→ Engineer reviews and approves
→ Requirement reaches "Accepted" status
→ Work item auto-created (status: To Do)
Manual
From the Requirements tab, approve a requirement and use the Create work item action on its row.
Work items can only be created for requirements with status Approved, Accepted, Implemented, or Verified. Draft and In Review requirements cannot have work items — this prevents premature implementation tracking and keeps only reviewed work in the delivery pipeline.
Each requirement can have one work item at a time.
Status lifecycle
| Status | Meaning |
|---|---|
| To Do | Backlog. Not started yet. |
| In Progress | Being actively worked on. |
| In Review | Awaiting reviewer or QA. |
| Done | Complete. The completion date is recorded automatically. |
You can change status from any view: drop on a Kanban column, pick from the row editor in List, or use the quick Start / Review / Done buttons.
Priority and estimates
- Priority: Low, Medium, High, or Critical. Shown as a coloured dot on Kanban cards and as a label in the List view.
- Estimate (optional): a story-point number. When every item in a sprint has one, Gantt and Insights switch to point-based completion. Leave it blank and metrics fall back to item-count.
Sprints
A sprint is a time-box with a start and end date that groups work items planned for delivery in that window.
Sprint lifecycle
| Status | Meaning |
|---|---|
| Planning | Scoped but not yet started. Add and remove items freely. |
| Active | The current sprint. Burndown and velocity charts target this one. |
| Completed | Finished sprint. Kept for historical comparison and velocity trends. |
Working with sprints
- In the Project tab, click Manage sprints in the top-right. Give the sprint a name, optional goal, and start/end dates.
- Assign work items to the sprint from the row editor (List view) or by dragging them in. Items without a sprint live in the Backlog.
- Use the Sprint filter dropdown above the board to focus on one sprint at a time. The Gantt view is the natural overview of all sprints together.
Sprint creation and editing live in the Project tab — that's where you plan and execute. The Insights tab is read-only metrics (burndown, velocity, team progress) and only shows a sprint selector so you can choose which sprint to chart.
Assignees
Assign work items to any active member of your organisation. Unassigned items show a dashed placeholder on Kanban cards.
The My Items tab is your cross-project view — every work item assigned to you, regardless of which project it belongs to. Use Open project ↗ on any row to jump into that project's full board.
Pushing to external tools
If Jira is connected for your organisation, the row editor exposes a Push to Jira action.
How to push
- Click Push to Jira on any work item that isn't already linked.
- Enter the Jira Project Key (e.g.
PROJ,DEMO). - Select an Issue Type: Task, Story, or Bug.
- Click Create Issue.
What happens
- A Jira issue is created with the requirement text, ID, and metadata.
- The work item is automatically linked to the Jira issue.
- The Jira issue key (e.g.
PROJ-123) appears as a clickable badge on the work item card. - Priority is mapped: Critical → Highest, High → High, Medium → Medium, Low → Low.
Requirements
- Jira must be configured at the project or user level (see Jira Integration).
- The Push to Jira button only appears when Jira is configured.
- Each work item can be pushed once — the button is hidden after linking.
Copy to AI
The Copy to AI action on any row copies a rich context bundle (requirement text + linked FMEA failure modes + relevant knowledge base entries) to your clipboard, formatted as Markdown. Paste it into your AI coding assistant of choice (Claude, Copilot, Cursor, ChatGPT) to get implementation help that already has the engineering context.
Insights tab
The Insights tab shows team-progress metrics for the active sprint:
- Burndown chart — remaining work vs. ideal pace over the sprint window.
- Velocity — points or items completed per sprint, trending across recent sprints.
- Sprint summary — items by status, by assignee, and by priority.
Insights are most useful once you have at least one completed sprint, since velocity is a rolling average.
Quick reference
| Action | Where |
|---|---|
| Create a work item | Requirements tab → row action, or accept an AI suggestion |
| Switch List / Kanban / Gantt | Top-right of the Project tab |
| Drag a card between statuses | Kanban view |
| Plan a sprint | Project tab → Manage sprints (top-right) |
| Assign a work item to a sprint | Row editor in List view, or the Sprint dropdown |
| See everything assigned to you | My Items tab |
| Push to Jira | Row editor → Push to Jira |
| Copy context for AI coding | Row action → Copy to AI |
Tier requirements
| Feature | Required tier |
|---|---|
| Work Items CRUD | Basic+ |
| Sprints, Kanban, Gantt | Basic+ |
| Push to Jira | Basic+ (with Jira configured) |
| Insights (burndown / velocity) | Advanced+ |
Check the Pricing page from the Help menu for the authoritative tier-to-feature mapping for your account.
Troubleshooting
"Work items require Approved+ status"
You're trying to create a work item for a Draft or In Review requirement. Move the requirement to Approved first.
"Push to Jira" button is missing
- Verify Jira is configured under Settings → Integrations → Jira.
- The work item may already be linked to a Jira issue — check for an existing Jira badge on the card.
- Confirm your plan includes the integration.
Kanban shows fewer cards than expected
Check the Sprint filter dropdown above the board. If it's set to one sprint or to "Backlog", only items in that scope appear. Click Clear filter to show everything.
Gantt is empty
The Gantt view needs at least one sprint with start and end dates. Create a sprint from the Insights tab.