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

# Work Items

> How Navigara joins sessions, pull requests, commits and issues into work items, and rolls them up to your objectives.

<video controls className="w-full aspect-video rounded-xl" poster="https://storage.googleapis.com/navigara-public-artifacts/docs/videos/work-items.jpg" src="https://storage.googleapis.com/navigara-public-artifacts/docs/videos/work-items.mp4">
  <track kind="captions" srcLang="en" label="English" src="/videos/work-items.vtt" default />
</video>

One piece of work leaves traces in many tools: agent sessions, pull requests, commits, and a tracker issue. Navigara joins these traces into one **work item**. Each work item shows what the work cost in AI spend, what it delivered in [ETV](/concepts/performance#the-etv-unit), and where it waited.

Work items also answer the alignment question: **is the work connected to planned objectives?**

## How Navigara joins the work

Navigara follows the links your team already makes. It does not ask you to tag work by hand.

* **Agent sessions and pull requests start work items.** A session or a pull request with no match starts a new work item.
* **Issues join when a session or a pull request names them.** For example, an issue key in a branch name or a pull request title.
* **Commits join through pull requests.** A commit joins the work item of the pull request that merged it into the default branch.
* **One work item has at most one issue.** Two different issues always stay in two different work items.

### Strong and weak links

Some links are stronger than others.

| Link | Examples | What it can do |
| - | - | - |
| **Strong** | A provider link between a pull request and an issue, a commit that a session made, a shared branch | Join a work item, or merge two work items into one |
| **Weak** | An issue key in a pull request body, an agent that only read an issue | Join a work item, never merge two |

Weak links never merge work items, so one stray mention cannot join two unrelated pieces of work.

Navigara also filters out noise. A bare key such as `PROJ-123` counts only if your organization has issues with that prefix. Trunk branches such as `main` link nothing.

<Note>
  Agent sessions link best when the AI tool reports branches and commits. See [AI tools](/integrations/ai-tools) for the telemetry setup.
</Note>

## What a work item shows

| Area | What you see |
| - | - |
| **AI spend** | Spend for each model, across all sessions in the work item |
| **Delivered work** | The ETV of the commits in the work item |
| **Flow** | The cycle from first to last activity, the review wait, and pull requests left open |
| **People** | The contributors, their agent sessions, and the models they used |

## Alignment

Work items roll up through your planning hierarchy. Navigara maps your tracker's structure to three levels:

| Navigara | Linear | Jira (default) |
| - | - | - |
| **Objective** | Initiative | Initiative, Theme |
| **Sub-objective** | Project | Epic |
| **Issue** | Issue | Other issue types |

In Jira, you choose which issue type goes to which level when you connect the tracker. Navigara ignores subtasks.

```
Work item → Issue → Sub-objective → Objective
```

Each level shows the AI spend and ETV of everything under it. You can start from an objective and see what it cost and what it delivered.

<Note>
  Lanes and flags are in preview. They can change before general availability.
</Note>

### Work outside the plan

Not all work links to an objective. Navigara places every work item in one of three lanes:

* **Roadmap**: work that rolls up to an objective.
* **KTLO**: upkeep work, such as maintenance and fixes. See [KTLO mode](/concepts/performance#ktlo-mode).
* **Unlinked**: work with no issue. This includes agent sessions that link to no issue, pull request or commit.

Navigara shows the unlinked share of AI spend, so you can find work with no home yet. Some unlinked work is normal: quick fixes, tooling, and experiments. A high share that keeps growing can mean that work happens outside the plan.

### Items to look at

Each level also flags work items that need a look:

* **Work after close**: activity on a work item after its issue closed.
* **Quiet items**: open work items with no recent activity.

<Tip>
  Start from an objective. Open the work items that cost the most, and ask what each one delivered.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.