Advanced planning in Jira: Overview of Jira Plans

When multiple teams are working toward the same goal, keeping everyone aligned gets complicated fast. Backlogs fragment. Priorities drift. Dependencies get missed until they become blockers.

Jira Plans is a cross-team planning tool available in Jira Premium and Jira Enterprise.

It pulls work from multiple projects and boards into a single project timeline, so program managers and team leads can track capacity, manage dependencies, and model delivery scenarios without disrupting individual team workflows.

This guide covers the key concepts of advanced planning to teach you what Plans is, how its core features work, and what to configure before your first Plan goes live.

What is Jira Plans?

Jira Plans is a cross-team planning feature that lets program managers coordinate work across multiple Jira projects from a single view. It supports capacity management, dependency visualization, scenario modeling, and a customizable work item hierarchy that extends above the epic level.

Multiple views for different needs

Plans offers several views, each designed to answer a different question. Switch between views depending on whether you're planning ahead, checking status, or managing capacity.

You can find these different views in the horizontal space navigation.

How Jira Plans brings work together

Jira Plans can pull in work from three different sources:

• Boards: Work items related to teams that track the volume and progress of their work.

• Spaces: Work items defined by a specific objective or deliverable, such as a product or feature.

• Filters: Work items defined by a query in Jira, otherwise known as JQL (Jira Query Language).

You can mix and match all three in a single plan. That means you can combine a team’s Scrum board, a space from a design team, and a filtered list of cross-functional dependencies—all in one view, without touching how any of those teams work day-to-day.

Work item sources define what data your plan pulls from Jira. You select them when you create a plan, and you can add or remove them at any time. Getting your sources right from the start is the fastest way to build a plan that reflects reality.

Once your work is in a plan, you can group, filter, and sort it by team, assignee, label, epic, sprint, or custom fields. For example, a program manager might group by team to see who's overloaded.

Or a VP might filter by initiative to check progress against a strategic goal, while an engineering lead might sort by dependency to find what's blocking the next release.

The same data, sliced differently for whoever's looking at it. Learn how to add or change issue sources in Plans.

How does the work item hierarchy work in Plans?

Plans starts with Jira's standard hierarchy—epics, stories, tasks, and subtasks—and lets you add custom levels above the epic to match how your organization structures work.

The default hierarchy levels are:

• Initiative (custom, above epic): A container for epics spanning multiple teams or spaces. Use this to represent a program or a strategic priority that cuts across team lines.

• Epic: A significant body of work broken into stories, tasks, and bugs. In a plan, epics represent a milestone or deliverable, and the work inside can be distributed across multiple teams.

• Story, task, or bug: The day-to-day work items your teams execute. Each can be assigned to a specific team within the plan.

• Subtask: A granular piece of work nested under a story, task, or bug.

You can customize and rename these levels to match how your organization talks about its work.

What is Program Board in Jira Plans?

Program Board is a feature within Jira Plans designed for program managers and business leaders who need to align delivery plans at the “team-of-teams” level. It provides a visual interface where each column can represent between 1 to 4 weeks iteration.

Each row represents a team included in your plan. With the Program Board, you can easily schedule work, manage dependencies, and keep everyone aligned.

This makes cross-team planning smoother and more transparent. Think of it as your bird's-eye view of a planning increment.

You’ll have every team's work laid out side by side so you can spot conflicts, handoffs, and bottlenecks before they become fire drills.

Why teams use Program Board

Teams use Program Board in several different ways—all depending on your cross-functional teams.

• Dependencies become visible, not verbal. Instead of relying on someone to mention "we're blocked on Team B," the connections are right there on the board.

• Cross-team alignment without the chaos. When five or ten teams are shipping toward the same goal, Program Board shows how all the pieces fit together.

• Live data, not a snapshot. Because it pulls from your plan in real time, the board stays current as work progresses.

How can teams manage capacity Jira Plans?

Capacity is the total amount of work a team can realistically take on in a given period. Knowing your team's capacity helps you set achievable timelines, spot overcommitment early, and make confident decisions when priorities shift.

In Jira Plans, capacity is visible directly on the timeline, so you can see at a glance whether a team is under- or over-allocated. Capacity planning is available to both scrum and kanban teams, though how each team measures it differs.

Both team types can track capacity in days or hours. Scrum teams can also use story points — a relative measure of effort — because their work runs in fixed-length sprints where estimating total effort per iteration is standard practice. Kanban teams work in a continuous flow without fixed iterations, so time-based measurement is the better fit.

How do teams manage releases in Jira Plans?

Releases mark the points in time when work needs to be complete. Depending on how your work is structured, a release can represent a shippable chunk of work, a release to customers, or a program increment.

Plans supports two types of releases:

• Single-space releases: Tied to one Jira project. These sync back to your Jira work items when you save changes.

• Cross-space releases: Span multiple Jira projects and let you align delivery dates across teams. Cross-space releases only exist in Plans—they aren't saved back to individual work items in Jira.

Any future releases already tied to a project in your plan appear automatically in the Releases tab. Use exclusion rules to remove releases (and their associated work items) that fall outside your plan's scope.

How do teams manage dependencies in Jira Plans?

In any project, some tasks can't start until others finish. These relationships — called dependencies — determine the critical path of your plan and directly affect whether work gets delivered on time. When dependencies are mapped clearly, teams can spot blockers early, adjust sequencing, and plan around risks before they become delays.

Jira Plans makes it easy to visualize, manage, and resolve dependencies, so you can spot blockers early and keep your projects moving forward.

Dependencies can be visualized in both the Timeline View as well as the Dependencies View

• Timeline View: See how work items are connected across your plan. Arrows between issues show which tasks depend on others, making it easy to spot potential bottlenecks.

• Dependencies View: Get a focused look at all dependencies in your plan, filter by team, sprint, or release, and quickly identify risks or conflicts.

Jira Plans: Frequently Asked Questions

What is the difference between Plans and the Jira timeline?

Jira timeline shows work within a single project. Plans is for coordinating work across multiple teams, spaces, and projects—with added features for capacity management, scenario modeling, and cross-team dependencies.

Is Plans available on all Jira editions?

No. Jira Plans is only available on Jira Premium and Jira Enterprise. Standard and Free editions include the basic timeline view, but not cross-team planning capabilities.

Does Plans change my data in Jira automatically?

No. Plans works as a sandbox. Any changes you make stay in your plan until you choose to save them back to Jira using the "Review changes" function. Your teams' live data is protected until you decide to commit.

How many teams can I include in a plan?

There's no enforced limit, but Atlassian recommends adding no more than 50 teams per plan for the best performance. For larger programs, consider splitting work across multiple plans.

Can you reuse a plan across teams?

Yes. Any plan can be duplicated in a few clicks. The copy carries over the same work items and settings as the original, so you don't have to rebuild your structure from scratch.

This is particularly useful for organizations that want to standardize how teams plan — create one well-structured plan, then duplicate it as a starting point for each new program or quarter.

Can I plan for both scrum and kanban teams in the same plan?

Yes. Plans supports both scrum and kanban teams as work item sources. Each team type measures capacity differently — scrum teams can use story points or time, while kanban teams use time only.

How do I share my plan with stakeholders?

Plans are made to be shared! Any view of any plan can be shared as direct link, embedded in a Confluence page for a live view, or exported as a CSV file or PNG image for a static view. Share settings are found in the top right corner of any Jira Plan.