# Release Analysis

Release Analysis shows delivery progress for one release: scope cards, issue-status totals and a burndown chart. It is distinct from [Launch Readiness](/docs/teams-projects/launch-readiness), which reports the release ship-readiness score.

## Open an analysis

1. Open the team and select **Projects → Release Analysis**.
2. Choose **Whole team (all apps)** or the project that owns the release.
3. Select a release. The active release is selected by default when available; otherwise the first release is selected.
4. Review issue status totals and scope cards. Scroll to **Sprint Burndown** for remaining work against the ideal trajectory.

![Team planning tabs, including Release Analysis](/docs/images/teams-projects/features-tab-navigation.webp)

The scope cards show **Committed**, **Completed**, and **Scope change**. Committed is work present at the release start date; Completed is done issues out of the current release scope; Scope change reflects issues added after release start.

## Date requirements

The status totals can display without dates. Burndown and scope cards need a **Start date**; the burndown also needs a **Target date**. If the chart area asks for dates, open **Releases**, edit the release, set both dates and save.

Analysis uses the selected release's assigned issues. If the release has no issues, add them from the [Releases](/docs/teams-projects/releases) tab.

## Troubleshooting

| Symptom                                | Check                                                                                  |
| -------------------------------------- | -------------------------------------------------------------------------------------- |
| No release is available                | Create one on the [Releases](/docs/teams-projects/releases) tab in the selected scope. |
| Burndown is not shown                  | Set both the release start date and target date.                                       |
| Counts do not match an expected sprint | Release analysis counts release-assigned issues; it is not a sprint analytics view.    |

For the readiness score and deployment/test-run inputs, see [Feeding Launch Readiness](/docs/teams-projects/launch-readiness).