Stories
A story is a single piece of work. Depending on what it represents, you can mark it as a task, a story, or a bug. Stories live inside a project, appear on the board, and can be grouped into sprints.
Creating a story
Add a story from the + on any board column, from the Add Story form in the backlog, or with the AI story generator. Only a title is required — everything else can be filled in later.
Story fields
| Field | Notes |
|---|---|
| Title | Required. Up to 500 characters. |
| Ref | An automatic identifier, unique within the project (for example WEB-12). |
| Type | task (default), story, or bug. |
| Description | Optional. Supports rich text. |
| Status | todo, in_progress, in_review, done, or cancelled. |
| Priority | critical, high, medium (default), or low. |
| Story points | An optional estimate (an integer). Fibonacci values such as 1, 2, 3, 5, 8, 13 are conventional. |
| Assignee | The person responsible. Unassigned by default. |
| Reporter | The person who created the story (set automatically). |
| Due date | An optional target date. |
| Sprint | The sprint this story belongs to, if any. No sprint means it sits in the backlog. |
| Labels | One or more coloured tags (see below). |
| Parent | A parent story, when this story is a subtask. |
When a story moves to In Progress its start time is recorded, and when it moves to Done its completion time is recorded. Those two timestamps drive sprint velocity and the burndown chart.
Subtasks
A story can have subtasks — smaller stories linked to a parent. Subtasks let you break a larger piece of work into checkable steps while keeping them grouped under the parent story. Subtasks appear on the parent's detail page.
Watchers
Watchers are people who want to follow a story without necessarily owning it.
- The person who creates a story automatically watches it.
- The assignee automatically watches a story when they are assigned.
- Anyone can start or stop watching with the Watch toggle on the story.
Labels
Labels are coloured tags scoped to a project. Create them under the project, give each a name and colour, then apply them to stories. Labels are useful for filtering the board (for example frontend, blocked, or customer-request).
Activity log
Every change to a story — status moves, field edits, assignment changes — is written to the story's activity log, giving you an audit trail of how the work evolved. The most recent activity is shown on the story detail page.
Links to other Hubrix items
A story can link to other objects in Hubrix:
- an agent,
- a workflow,
- a research report,
- a document, or
- a chat.
This keeps a work item next to the AI artefact it relates to — for example, linking a "Ship Q3 report" story to the research report and the workflow that generate it.
Deleting a story
Open the story and choose Delete Story. Deleting a story also removes its subtasks, labels, watchers, links, and activity. This cannot be undone — if you only want to take a story off the board, set its status to cancelled instead.
Was this helpful?