The Product Goal is the one long-term aim a project's backlog works towards. It sits in a card at the top of the backlog (Scrum and Kanban projects), and it's shown under the Sprint goal field when anyone creates or edits a sprint — so every sprint goal can point back to it.

Set or change the Product Goal

1. Open the Backlog. With no goal yet, click Add Product Goal; otherwise click Edit on the Product Goal card.
2. Write the aim in a sentence or two — up to 1,000 characters.
3. Click Save. The card shows who last updated it, and when. Saving an empty box removes the goal.

Goals are what your organisation is working towards, measured by key results and linked to the work that moves them. Owners, Admins and Members work with goals on the Goals page in the sidebar, and organisation Stakeholders can read them. A goal on a private project is visible only to people who can open that project.

Create a goal

1. Click New goal. Give it a Title and, if you like, a Description.
2. Choose the Type — Company, Team or Project (for a project goal, pick the Project too). You only see the types you're allowed to create.
3. Set its Status, an optional Period (such as "Q4 2026"), Target date and Pod, then click Create goal.
4. Open the goal and click Add key result: name the number that shows success, how it's measured, its Start, Target and Unit. The goal's progress follows its key results.

Check in and keep the status honest

1. On a key result, click Check in, enter the Current value and, if it changed, its status (Not started, In progress, Achieved or Missed). Click Save check-in.
2. Change the goal's own status from the Goal status menu: Draft, On track, At risk, Achieved or Missed.
3. Filter the page by type, status or pod to see just the goals you care about.

Link work to a goal

1. Open a work item and find its Goals section. Goals that fit (by project, team or pod) are listed under Suggested — click one to link it.
2. The goal then lists the item under its linked work items, so people can see what moves it. Remove a link with the × beside it on the work item.

The roadmap draws each epic as a bar from its start date to its due date, with the finished part filled in, so the whole team can see when the big pieces land. It reads straight from your epics — there's nothing to set up on this page. Every role on the project can open it.

Read the roadmap

1. On a wide screen, choose how much time to show with Weeks, Months or Quarters.
2. Also on a wide screen, move along the timeline with Earlier and Later; Today jumps back. A Today line marks the current day.
3. On a Scrum project, a sprint lane along the top (wide screens) shows your sprints, so you can see which sprints an epic spans. Click a running or completed sprint to open its board, or a planned one to open the backlog. Kanban projects have no sprint lane.
4. An epic past its due date and not done is marked overdue, with how many days. Completed epics are hidden until you tick Show completed epics.

Put an epic on the roadmap

1. Epics with no dates are listed under Not scheduled, with how much of their work is done.
2. Click Set dates beside one, and give the epic a start date and a due date (the due date can't be before the start).
3. Its bar appears on the timeline. Setting dates is for whoever can edit work items on the project: the Product Owner, Scrum Masters, Developers and Admins.

A version groups the work that ships together. Releases has two tabs, Unreleased and Released, and every project role can read them. Each version has its own page, named by the version (for example …/releases/2.4).

Create a version and fill it

1. Click New version. Give it a Version name, an optional Start date, Release date and Description.
2. Add work to it by setting a work item's Fix version (anyone who can edit the item can do this).
3. Each unreleased version shows a due pill, worked out in the project's timezone: 5 days left, Due today or 3 days late.
4. Open a version to see its Work items grouped as To do, In progress and Done, with who's working on them.

Release a version

1. Click Release on the version.
2. Check the Release date. If some work isn't finished, choose under Unfinished work: Leave on this version, or move it to another unreleased version.
3. Click Confirm release. It moves to the Released tab, which says whether it went out on time or how many days late.
4. Released by mistake? Use the version's ⋯ › Unrelease…. Edit… and Delete… are in the same menu.

Share the release notes

1. Open the version and choose the Release notes tab.
2. The notes are built for you from the version's finished work items — there's nothing to write.
3. Click Copy and paste them into a changelog or an announcement.

Components split a project into the parts of the product it owns — for example "Payments" or "Mobile app". Each component can have a lead, who becomes the assignee of new work items with that component and no assignee.

Set up components (leads)

1. Open Project settings › Components and click New component.
2. Give it a Name (unique in the project, ignoring capitals), an optional description and an optional Lead.
3. Rename one with ⋯ › Edit — every work item picks up the new name. Deleting a component removes it from its work items; the items stay, and each gets a History entry.
4. The list is sorted by name. The work item count beside a component opens the backlog filtered to it.

Use components on work items

1. In a work item's Components field, pick from this project's components (up to 20 per item). Anyone who can edit the item can do this.
2. When you create an item with a component and leave the assignee empty, the component's lead becomes the assignee. Choosing an assignee yourself, or changing components later, never changes who it's assigned to.
3. In the backlog, filter by component (or No component) to see one part of the product.
4. A CSV export includes a Components column. Importing our CSV template matches component names to the ones already in the project; unknown names are skipped with a warning.