---
title: "Delivery"
description: "Sprint board, backlog, bug tracker and work logs — the day-to-day execution surface."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.heizen.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery

Delivery is where groomed work gets executed and tracked.

## Sprint Board

The active sprint, story by story. Stories move across the board as they
progress; a sprint has a start and end and can be created, updated or closed
from here.

## Backlog

Everything not yet in a sprint, grouped by epic. Stories can be created by hand
or generated from [requirements](/studio/product), moved between epics, and
pulled into a sprint when they're ready.

## Bug Tracker

Bugs carry a status, priority, assignee and comment thread. When a bug turns out
to be scope rather than a defect, convert it straight into a user story — it
keeps the history and lands on the backlog.

## Work Logs

Time logged against a story or a bug, so effort stays attached to the work it
belongs to rather than a separate timesheet.

## Jira board

Projects linked to Jira get a Jira Board view alongside the native one, and
stories can be pushed to or pulled from Jira — see
[Integrations](/studio/integrations).

> **Do this from your editor**
>
> Bugs, stories, epics and sprints are all in the `core` toolset over
> [Heizen MCP](/mcp/tools) — `list_bugs`, `create_story`, `create_sprint`,
> `convert_bug_to_story` and the rest. The `triage_my_bugs` and `daily_standup`
> [prompts](/mcp/prompts) are built on them.

Source: https://docs.heizen.work/studio/delivery/index.mdx