See cross-team work clearly with Plans in Jira - Public Learning Session 27th August

[#1]

Thanks to everyone who joined the class! We had some great questions and a very focused group. We covered how Plans in Jira gives you one place to see timing, dependencies, and capacity across the work that matters.

In this live session, we explored how to use Plans to move from a list of work items to a view that helps you make planning decisions. The group included people working in a single team, people coordinating across multiple spaces, and people preparing a move from spreadsheets or Microsoft Planner.

Start with a useful planning question

Plans work best when they answer a specific question. This is where the plan stops being a polite timeline and starts pointing at what needs attention:

• Which work needs to happen first?

• Where are dependencies likely to delay delivery?

• Does a team have more work than it can realistically take on in a sprint?

• What changes if we move work, dates, or people?

We used two examples in the session. A single-team Spring Fair plan showed how epics, work items, dates, and blockers roll up into a timeline. A multi-team office-move plan showed how to bring work together, add teams, and inspect capacity across sprints.

To start your own plan, select the + next to Plans in Jira, choose the work sources to include, then select Create.

Use the right view for the decision

Plans offers more than one way to inspect the same work.

• Timeline helps you understand sequence, dates, and dependencies.

• List removes timeline bars so you can add columns and review work item detail.

• Summary brings together built-in health signals, including progress, key dependencies, and team capacity.

• Capacity helps you see when planned work exceeds a team's available capacity.

The Summary is designed as a health view with overview cards and widgets. To tailor the detail you review, use List or Timeline with the plan’s filters, grouping, and saved views. If capacity planning is enabled and your plan includes team sprints, the Program board also shows an abbreviated sprint-capacity view.

Test changes before you apply them

Plans lets you make unsaved changes while you explore options. You can try moving dates or reassigning work, inspect the impact, and decide whether to apply the change back to Jira. That makes the plan a practical space for planning conversations, not only a reporting view. Think of it as a planning sandbox, but with stronger opinions about dates.

Keep dependencies in the work

Dependencies are created on Jira work items and then become visible in the plan. This is useful when work crosses teams because it exposes the sequence behind a delivery date. You can also create dependencies from the plan when you spot a relationship that needs capturing. The red-string-on-a-corkboard approach remains entirely optional.

One participant asked about using Plans with 18 or more teams in a single space. Set up the relevant Atlassian teams, assign work to those teams, and use teams when capacity is part of the question. The number of teams in one space does not prevent you from planning the work together.

Try it yourself

Create a small plan from work you already own. Add one team, one date range, and one dependency. Then switch between Timeline and Capacity to see which view gives you the clearest answer to your next planning question. Start small, then build from there.

Watch the session recording

Register to watch the session recording in Zoom.

Keep learning with free classes

Want to build your Jira planning skills further? Explore the Atlassian Community Learning calendar to find upcoming free classes, live learning sessions, and opportunities to learn alongside other Atlassian users.

See you in the next session!