Excluding releases from your plan
Releases
On this page
Related content
- Installing Java for Confluence
- Setting the JAVA_HOME Variable in Windows
- How to switch from the bundled JRE to System Java when using Confluence as Windows Service
- How to use system Java instead of the bundled JRE
- Confluence Service stops after a few seconds; Confluence Service won't start
- Start Confluence Automatically on Windows as a Service
- Windows Service failed to be created due to JAVA_HOME environment variable configuration
- Confluence Cannot Start Due to 'Unsupported major.minor version 49.0'
- Upgrade to Confluence 5.8.x failed due to Unsupported major.minor version 52.0 (unable to load class com.atlassian.confluence.setup.ConfluenceConfigurationListener)
- Unable to start Windows Service due to "Failed creating java jvm.dll" "The specified module could not be found"
This page discusses the usage of Portfolio for Jira live plans (any version from 2.0 to 2.27). 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:
- Go to your plan via Portfolio (in header) > View Portfolio > click 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
> 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 > 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 topics
Related content
- Installing Java for Confluence
- Setting the JAVA_HOME Variable in Windows
- How to switch from the bundled JRE to System Java when using Confluence as Windows Service
- How to use system Java instead of the bundled JRE
- Confluence Service stops after a few seconds; Confluence Service won't start
- Start Confluence Automatically on Windows as a Service
- Windows Service failed to be created due to JAVA_HOME environment variable configuration
- Confluence Cannot Start Due to 'Unsupported major.minor version 49.0'
- Upgrade to Confluence 5.8.x failed due to Unsupported major.minor version 52.0 (unable to load class com.atlassian.confluence.setup.ConfluenceConfigurationListener)
- Unable to start Windows Service due to "Failed creating java jvm.dll" "The specified module could not be found"