# Plan a release, ship it, and write its changelog > How a release groups the work items that ship together, from turning releases on and setting the scope to shipping it and writing its changelog. Lesson 7 of 12 in Plane Business · 4:07 · [Watch the lesson](https://academy.plane.so/videos/releases) ## Chapters - [0:00](https://academy.plane.so/videos/releases?t=0) Know what shipped - [0:31](https://academy.plane.so/videos/releases?t=31) Turn on releases and plan one - [1:29](https://academy.plane.so/videos/releases?t=89) Decide what goes in - [2:37](https://academy.plane.so/videos/releases?t=157) Ship it and write it up - [3:46](https://academy.plane.so/videos/releases?t=226) See every release by status ## Know what shipped A release in Plane is a set of work items that ship together, with a target date, a lead, a version tag, and labels. It shows what a version holds and how close it is to done. After it ships, its changelog tells the team what went out. Releases are on Business and higher. ## Turn on releases and plan one A project admin switches on **Enable Releases** in **Project settings**, under **Features**, then **Releases**. The project's sidebar then lists **Releases**, and the same settings page holds the project's own release tags and labels. 1. Choose **Add release** and name it. No two releases in the workspace can share a name, even across projects. 2. Set a target date and a lead. 3. **Tag** takes one version number. Typing a new one adds it on the spot. 4. Add as many labels as you need, then choose **Create Release**. Every release starts as **Unreleased**. You move it to **Released** or **Cancelled** yourself. Finishing every work item doesn't release it, and a cancelled release keeps its work items. ## Decide what goes in A release's scope is the work items it ships. 1. On the **Scope** tab, choose **Add work items**. 2. Check the ones you want, and add them. A project release takes only its own project's work items. Adding one leaves its state, assignees, and cycle as they were. To take a work item out, choose **Remove from release** in its menu. It stays in the project. Each work item also has a **Releases** property in its details, and anyone who can edit the work item can set it. With **Releases** on under **Display**, you can set it in the list, board, or table layout. One work item can sit in several releases. The **Overview** tracks **Progress**: completed, pending, and cancelled work items. Cancelled ones drop out of the total, so they don't pull the percentage down. Beside it, **Activity** records each change and who made it, including every work item added or removed. ## Ship it and write it up 1. When the work is ready, choose **Release now**. If some work items are still open, Plane asks what to do with them. 2. Choose **Transfer unresolved work items** to move them into another unreleased release in the same project, or **Ignore unresolved work items** to leave them in place. 3. Check the date it ships, then choose **Release**. Plane saves that date and sets the status to **Released**. Neither choice changes the open work items' state, and a work item that moves keeps any other release it's in. The **Changelog** tab is a document for what went out. Anyone who can edit the release can write it, before or after shipping, and it saves as you type. Workspace releases work the same way, but take work items from any project, so one release can cover several teams. A workspace admin turns them on in **Workspace settings**, under **Features**, then **Releases**, and they appear under **More** in the sidebar. ## See every release by status One project now ships in releases, each with its scope and changelog, listed by status as **Unreleased**, **Released**, or **Cancelled**. ## Try it Open Project settings, then Features, then Releases, and switch on Enable Releases. Then choose Add release, name it, and set a target date, a lead, and a tag. ## Plans - Business: Releases ## Docs - [Project releases](https://docs.plane.so/projects/project-releases) - [Workspace releases](https://docs.plane.so/releases) ## Transcript ### Know what shipped A release in Plane is a set of work items that ship together, with a target date, a lead, a version tag, and labels. It shows what a version holds and how close it is to done. After it ships, its changelog tells the team what went out. In one project, you'll turn releases on, create one, set its scope, ship it, and write its changelog. Let's take a closer look. ### Turn on releases and plan one On Business and higher, a project admin switches on Enable Releases in Project settings, under Features, then Releases. The project's sidebar then lists Releases, and the same settings page holds the project's own release tags and labels. Project admins choose Add release and name it. No two releases in the workspace can share a name, even across projects. Set a target date and a lead. Tag takes one version number, and typing a new one adds it on the spot. Add as many labels as you need, then choose Create Release. Every release starts as Unreleased. You move it to Released or Cancelled yourself. Finishing every work item doesn't release it, and a cancelled release keeps its work items. ### Decide what goes in A release's scope is the work items it ships. On the Scope tab, choose Add work items, check the ones you want, and add them. A project release takes only its own project's work items. Adding one leaves its state, assignees, and cycle as they were. To take a work item out, choose Remove from release in its menu. It stays in the project. Each work item also has a Releases property in its details, and anyone who can edit the work item can set it. With Releases on under Display, you can set it in the list, board, or table layout. One work item can sit in several releases. The Overview tracks Progress: completed, pending, and cancelled work items. Cancelled ones drop out of the total, so they don't pull the percentage down. Beside it, Activity records each change and who made it, including every work item added or removed. ### Ship it and write it up When the work is ready, choose Release now. If some work items are still open, Plane asks what to do with them. Choose Transfer unresolved work items to move them into another unreleased release in the same project, or Ignore unresolved work items to leave them in place. Neither choice changes their state, and a work item that moves keeps any other release it's in. Check the date it ships, then choose Release. Plane saves that date and sets the status to Released. The Changelog tab is a document for what went out. Anyone who can edit the release can write it, before or after shipping, and it saves as you type. Workspace releases work the same way, but take work items from any project, so one release can cover several teams. A workspace admin turns them on in Workspace settings, under Features, then Releases, and they appear under More in the sidebar. ### See every release by status One project now ships in releases, each with its scope and changelog, listed by status as Unreleased, Released, or Cancelled.