Managing teams and releases
Portfolio for Jira Home
- Discovering Portfolio for Jira
- Getting started with Portfolio for Jira
- Administering Portfolio for Jira
- Setting up the planning environment
- What is a Portfolio plan
- Working with Portfolio plans
- Managing teams and releases
- Saving changes in Jira
- Sharing roadmaps
- Portfolio for Jira live plans (versions 2.0 to 2.27)
- Portfolio for Jira Server GDPR support guides
On this page
- No related content found
Still need help?
The Atlassian Community is here for you.
This page refers to the usage of the improved planning interface in Portfolio for Jira (version 3.0 and later). If you're using a Portfolio for Jira live plan (any version from 2.0 to 2.27), refer to the documentation in this section.
While planning work for your teams in the improved interface, it's worth monitoring every now and then the existing teams and releases in your plan. This is especially helpful when you're frequently auto-scheduling your plan — the teams and releases in your plan do have an impact in how work is scheduled in your plan, and even how fast your plan performance can be.
For example, you may notice that your team capacities are becoming more and more overbooked over time. You may need to check the weekly hours or velocity that you've set for your teams. Or perhaps you need to add more members to an overbooked team, so that team has more capacity to work with.
You may also want to consider removing releases that have been completed from your plan. Over time, your plan may be collecting releases that you no longer need to monitor. By removing these releases, you can increase the loading performance of your plan.
Check out the following pages to know more: