Using the later release
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.
All projects have what is called a later release. When calculating a plan, Portfolio for Jira does the following:
- Portfolio searches for issues that do not have any release assigned to them.
- If such issues are found, Portfolio checks if these issues can be scheduled, i.e. the issues have already been estimated.
For issues that can be scheduled, Portfolio then calculates the issues into an available release. If there are no available releases (e.g. all releases are already filled up), then Portfolio will schedule the issues to a later release.
This later release has a dynamic end date, depending on the items that are scheduled into that release. The later release always starts after the last defined release ends.
- A fixed end date release is completely filled up, some epics or stories could not be scheduled into it anymore. These get pushed back into the later release.
- A release with a dynamic end date is defined (let's say release "2.0"), but no backlog items are assigned to it. In this case, it is assumed that these items are not supposed to be in the scope of "2.0". Otherwise, they would need to have a fixed assignment to it. As a result, backlog items with release set to "Calculate" will get pushed into the later release.
- No releases are defined at all - in that case everything is scheduled into the later release as well and you see the projected completion date as the end date of the later release.