/
The Native Jira Planning Experience: How It Works

Try Advanced Release Planning for Jira Cloud free for 30 days

The Native Jira Planning Experience: How It Works

This page explains how the planning surface in Release Management, Roadmaps & Product Portfolio for Jira is delivered as a native Jira experience, and how its core interactions behave. It is a neutral reference doc; for the narrative version, see the linked blog post at the bottom.

What "native" means

Release Management, Roadmaps & Product Portfolio is a Forge app that Runs on Atlassian. Its interface is built with the Forge UI Kit and the Atlassian Design System — the same design language used across Jira. As a result, the planning board renders inside Jira and follows the interaction patterns Jira users already know, rather than opening a separate external application.

Because the app reads and writes the issues already in your Jira project, there is a single source of data. No import, export, or synchronization step is involved.

Core interactions

Inline card editing

Fields such as story-point estimate, assignee, and status can be edited directly on a card in the planning view. Edits are written to the underlying Jira issue immediately, so the value shown in the planner and the value on the issue stay identical.

Chevron (epic) expansion

Epics display an expansion chevron. Selecting it reveals the epic's child issues in place, using the same expand/collapse pattern found elsewhere in Jira, without navigating away from the planning board.

Native Atlassian patterns

The interface runs in the browser using Atlassian Design System components, so controls, spacing, and behavior match standard Jira UI. No additional login is required beyond the user's existing Jira session.

Why this reduces context switching

Planning, scoping, and forecasting all take place on one surface inside Jira. Because the same view reads the project's real issue and throughput data, a probabilistic (Monte Carlo) forecast can be produced without moving data into a separate tool. Users do not need to reconcile a planning tool, a spreadsheet, and Jira as three separate copies of the plan.

Related