The Team planning page
The Team planning page focuses on one team’s plans for an Increment. Here, a team can make plans to execute the big goals for the Increment.
Each team board in a Program has a Team planning page for each Increment.
Plan story-level work from the backlog or synchronize sprints for scrum teams.
You can select additional teams to view and manage interdependent plans.
Use the Team planning page to:
Connect work from your team backlog to Objectives and to the big plans on the Increment roadmap.
Manage dependencies within the team and with other teams.
Estimate work and schedule according to sprint capacity.
Align and commit on plans, including a confidence vote.
Connecting to high-level plans
Roadmap items
Roadmap items will show in purple at the top of the page. This will include:
Items in this team’s swimlane on the roadmap
Items from the “Shared team features” swimlane
Click a roadmap item to show its children. This will also filter items in the Team backlog panel.
When the roadmap item is selected, quick-creating new items will link to that roadmap item automatically.
If your roadmap is only epics (or epic-level items), this uses the parent-child relationship in Jira: an epic is the Parent of a Story.
When the Roadmap issue source “Any issue types from a dedicated board“, the link between roadmap and team-level items is configured manually for the Program.
PI Objectives
Create and manage PI Objectives from the 🏆 “Team PI objectives” button.
Click “View progress” to jump to the Objectives report.
Learn more about PI Objectives.
Scheduling work
Schedule items using drag-and-drop to make plans for your team.
For Scrum boards, columns are synchronized with sprints from Jira. Dragging items into/between columns will update the Sprint field.
For Kanban boards, sprints will only be used when the Increment’s Sprint source is “shared sprints from a dedicated board” and the Sprint field is available on the item in Jira.
Open the “Team backlog” panel to schedule items from this Jira board that aren’t yet scheduled in this Increment.
Learn more about scrum and sprints in Easy Agile Programs.
Creating new items
Quick-create an item in any column.
The sprint field will be set automatically (where applicable).
When a roadmap item is selected, quick-creating new items will link to that roadmap item automatically.
If there are required fields, the “Create item” dialog will pop up so you can finish creating the item.
If the board filter query only includes items with specific fields, newly-created items may disappear on page refresh.
When the query specifies a single Component or Label, the app will attempt to complete that field.
Estimation and sprint capacity
Easy Agile Programs can use Story points from Jira to manage estimations and capacity.
This is available for scrum boards where the Estimation Statistic is set to “Story points”.
See and edit the Story point estimate for each item in the bottom-left corner of the card.
Set a capacity for each sprint at the top of the column, and compare it to the total estimate of scheduled items.
Learn more about estimation and capacity.
Confidence voting
Find the “Confidence vote” button in the top right-hand corner of the Team planning page.
Votes on the Team planning page are separate from the vote on the Program board page or on other Team planning pages.
Cross-team work
Use the “Other teams” button to add one or more additional teams to the page.
A 
“Warning” icon will show on the button when there are cross-team dependencies.
Seeing the details
Dependencies
Dependency lines visualize links between items in Jira. Manage and create dependencies on the Team planning page.
Issue links in the Jira Data Center issue view
Dependency lines on the Team planning page in Easy Agile Programs
Learn more about dependencies.
Filtering
Find the “Filters” button at the top of the page to apply Quick filters from your Jira board.
Quick filters use a snippet of JQL to find only items that meet certain criteria. This makes them extremely flexible: you can create a Quick filter that suits your team’s needs.
Board administrators can configure Quick filters in Jira Cloud or Jira Data Center.
Quick filters are not available for team-managed projects.
If the roadmap is sourced from a dedicated board, you’ll also be able to apply Quick Filters from that board to the roadmap-level (purple) items on the Team planning page.
Alternatively, filter by PI Objectives.
Show extra fields on cards
Flagged items will be highlighted on the Team planning page, just like on the Backlog in Jira.
Learn more about customizing cards.
Troubleshooting
New item disappears after page refresh
The team in Easy Agile Programs is managed with a Jira board. The board’s filter query controls what Jira items are in the board.
Some board filters require a specific field. Teams working on part of a project(s) might use a board filter such as:
project = ABC AND component IN (iOS, Android)project IN (ABC, XYZ) AND label = iOS
This means that newly-created items can sometimes disappear from a board if they don’t yet meet the criteria. For example, a new item with no component set will disappear from a board with a component in the board filter.
Easy Agile Programs will attempt to auto-fill fields where possible. Only standard Jira fields, such as component and label, are auto-filled.
Whether the app can auto-fill will depend on how many possible values are specified in the board filter:
For
project = ABC AND component = iOS, the app will add the component “IOS”.For
project = ABC AND component IN (iOS, Android), the app cannot determine which component to add, so it can’t auto-fill it.
New item failed to link to selected parent item
When a roadmap item is selected, quick-creating new items should link to that roadmap item automatically. This can fail when:
The Roadmap issue source is “Any issue types from a dedicated board”; AND
The link type configured for the team-to-roadmap connection is “Parent”.
The item will be created, but it can only be linked to its parent if the “Parent” field is available to edit in Jira.
When an item fails to link with a parent, a message appears in the bottom left corner with a link to clear all filters so that you can easily see the newly created item.
Cloud:
Linking an item to a roadmap item will fail if the item is being created for a team-managed project, as items in team-managed projects cannot be children of items in other projects.
Linking an item to a roadmap item will fail if the parent-child relationship doesn’t match the hierarchy configured in Jira. For example: by default, an Epic can be “parent of” a Story, but not the other way around.
Data Center: Linking a new issue to a roadmap issue will fail if the “Parent” field is not editable on the item. To resolve this problem, a Jira Administrator will need to add the Parent field to the Screen in Jira. Learn more about configuring fields for issues on Jira Data Center.