Excluding releases from your plan
Releases
On this page
Related content
- The diff in pull requests is showing unrelated files after upgrade of Bitbucket Server or Data Center to 7.x or 2-way diff change.
- Comparison of a Pull Request Diff between Bitbucket Server and Data Center versions up to 6.x and from 7.x onwards
- Understanding Diff view in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- PR Diff shows different content from the actual file content in Bitbucket Datacenter
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- How to diff arbitrary commits using REST API
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Different file content for the same commit is being displayed in Bitbucket Server
This page discusses the usage of Advanced Roadmaps live plans. If you're using the redesigned planning interface, see this page instead.
Releases can be excluded to change the scope of your plan. Issues assigned to excluded releases will no longer appear in your plan.
Follow these steps to exclude an existing release from a plan:
- In your plan, click the Releases tab to display the releases section below the timeline.
Select the release you want to exclude.
If the release hasn't been committed to Jira, hover over the release, click more (
) > Delete.
This operation will permanently delete the release and any issue assigned to this release will be settled to "Calculate".
If the release is already committed to Jira, hover over the release, click more () > Exclude from plan.
If an issue is assigned to multiple different release in Jira and only one of them is excluded, the issue will be still be a part of your plan.
Related content
- The diff in pull requests is showing unrelated files after upgrade of Bitbucket Server or Data Center to 7.x or 2-way diff change.
- Comparison of a Pull Request Diff between Bitbucket Server and Data Center versions up to 6.x and from 7.x onwards
- Understanding Diff view in Bitbucket Server
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- PR Diff shows different content from the actual file content in Bitbucket Datacenter
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- How to diff arbitrary commits using REST API
- Bitbucket Server/Data Center shows diff between branches even after they are merged (using squash commit)
- How to find the commit that introduced an unexpected change in Bitbucket Server and Data Center
- Different file content for the same commit is being displayed in Bitbucket Server