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

# Projects

> Track progress on projects and debug issues causing them to slip

<Tip>
  In Weave, we call a collection of tasks a "project". In Jira, it's called an
  "Epic".
</Tip>

## How it works

For every project in your project management system, Weave takes a snapshot of the project state
every day. Then it tracks how the project changes over time, including:

* Tasks that were unplanned when the project started that were later added
* Scope changes from adding, removing, or re-estimating tasks

When you filter by date range, a project is included if it or any of its child tasks had activity
during that period (not only if the project was created in the range).

Unless you narrow the status filter, the projects overview lists projects in every status (planned, in progress, completed, and so on). Use the **Planned** or **Started** status chips to focus on a subset.

For Jira epics, you can optionally show each project's source issue key (for example `PROJ-456`) in an **Issue number** column. Turn this on under **Organization settings** → **General** → **Projects** → **Display project identifiers** (off by default). Linear projects do not have an equivalent identifier.

Wherever possible, Weave ties back **estimates** from tasks to the actual **output** associated with
them. For example, the project focus percentage pie chart is based on the percentage of **output**
for each contributor that went to the given project (as opposed to story points or something else).

## Projected finish date

Weave forecasts when each in-progress project will finish, based on how fast the work is actually being delivered.

1. **Estimate the total work.** Weave converts the project's task estimates into [code output](/metrics/code-output), using how much output the already-completed tasks took relative to their estimates.
2. **Measure the pace.** It compares the output completed since the project's start date with the time elapsed.
3. **Extrapolate.** At that pace, the remaining work gives the estimated finish date.

You also get a range: the earliest date assumes the team delivers 1.5× faster than its current pace, and the latest assumes half the current pace.

The estimate appears in the **Estimated completion date** column on the projects overview and as a projection on each project's progress chart, so a slipping project shows up as a finish date moving later.

Weave doesn't show a forecast when it can't make a meaningful one: the project has no start date, no completed output yet, no progress since it started, or its completed output already meets the estimated total.

## Linking pull requests

Weave links PRs to projects and tasks automatically when issue keys appear in PR titles, descriptions, or branch names (see [Task-to-code linking](/project-management/overview#task-to-code-linking)).

You can also **manually link PRs** from a project report: use the PR picker on the project page or on individual task rows to search your organization's pull requests and attach or detach links. Manual links count toward project progress and output the same way automatic links do.


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