TechPrufer
Get started
Atlassian
Atlassian logoAtlassian · Feature trail

Jira Product Discovery Capacity Planning

13 posts · Mar 2018 – Aug 2026

What this trail covers

Jira Product Discovery (JPD) is evolving into a comprehensive capacity planning and project budgeting tool. New features include individual capacity planning with detailed bandwidth allocation (hours, percentages, days), accounting for leave and operational work. Formula fields allow for custom calculations directly on work items, enabling dynamic project budgeting, ROI tracking, and at-risk flagging. Space insights provide live, custom dashboards connected to work data, with AI-driven chart generation. This post details how engineering leaders can leverage JPD to create four key views: a helicopter view for strategic alignment, a high-level capacity planning view to identify resource constraints early, a backlog prioritization view for balancing tech debt and new features, and a delivery dashboard for real-time progress updates to stakeholders. These views aim to improve communication, decision-making, and resource allocation for engineering teams.

All Atlassian trails
  1. Jira goes where spreadsheets can’tThis post introduces individual capacity planning within Jira, allowing teams to allocate bandwidth for team members across multiple projects, accounting for leave and operational work. It also details the addition of formula fields, enabling custom calculations on work items for project budgeting, ROI tracking, and at-risk flagging. The post highlights the integration of Rovo AI for natural language interaction with these new features, including capacity plan updates and formula creation. Space insights are enhanced with AI-driven dashboard generation and plain-language trend explanations.
  2. They committed to 60 engineers' worth of work with 35 engineersThis post details how Jira Product Discovery (JPD) was used to build a live capacity planning view. The author created dedicated views for two engineering teams (Quakus and Ragents), structuring them with monthly engineer columns to track committed capacity. A 'resourcing' column (yes/no) indicates if a project is staffed, and a hard capacity target (e.g., 11.5 engineers per month) serves as a ceiling. The system exposed a front-end constraint, leading to the creation of a companion timeline view grouped by engineer, visualizing project bars and the backlog. This view allows for dynamic assignment of backlog items and auto-adjustment of dates. The post highlights the shift from spreadsheet-based planning to evidence-based decision-making using live data within JPD.
  3. How one PM replaced status updates with a live system of truthThis post details how Jira Product Discovery's published views can be leveraged as a live, read-only source of truth for roadmaps, reducing the need for manual rewriting and status updates. It describes the creation of a 'mega board' organized by workstream with various fields, which stakeholders can bookmark and access for current information. The post also highlights the use of Rovo AI to generate Confluence roadmap pages from JPD views, and the strategic shift for Product Managers from status reporters to system owners.
  4. 4 Views in Jira Product Discovery Every Engineering Leader NeedsThis post introduces four specific views within Jira Product Discovery that engineering leaders can utilize: a 'helicopter view' for strategic alignment and justifying technical investments, a 'high-level capacity planning' view to identify potential resource constraints and inform discussions about trade-offs, a 'backlog prioritization' view to balance tech debt with new features and facilitate data-driven discussions, and a 'delivery dashboard' for real-time progress updates to stakeholders by connecting initiatives to Jira epics and issues. It provides tips for setting up these views and explains their benefits for engineering leaders.
  5. Portfolio for Jira Server and Data Center 3.0 has arrivedThis post details the highlights of Portfolio for Jira Server and Data Center 3.0, focusing on enhanced user control for roadmap creation, evolution, and sharing. New features include drag-and-drop functionality for re-parenting and reordering issues, color-coding and swimlanes for visualization, on-the-spot plan editing, and an auto-schedule algorithm that considers backlog priority, estimates, and dependencies. The release emphasizes seamless integration with Jira Software and improved performance and scaling capabilities.
  7. How KodaCloud moved off Excel and onto Portfolio for JiraThis post details how KodaCloud uses Portfolio for Jira (now Jira Product Discovery) to manage cross-team planning, capacity, and stakeholder alignment by leveraging scope tables and release reports to visualize epics and their stories, and capacity reports to ensure achievable sprints. It also outlines KodaCloud's approach to building a Portfolio plan by pulling in Scrum boards and projects as issue sources, and using Jira versions as Portfolio releases with sprints as sub-milestones.
  8. Forecast realistically with Portfolio for Jira Server's APIIntroduces REST and JAVA APIs for Portfolio for Jira Server, enabling integration with external HR systems to pull team availability data (e.g., time off). This automates the reflection of employee data into plans, improving forecast accuracy and identifying dependencies/bottlenecks. Also enables enterprise-grade reporting by allowing external systems to pull team details from Portfolio for Jira.
  9. Quri Portfolio for Jira case studyThis post details how Quri uses Portfolio for Jira to gain visibility into team work, identify bottlenecks, and improve roadmap feasibility. It highlights the benefits of automatic updates from Jira Software, improved work breakdown by the engineering team, and better capacity planning for leadership.