Introduction to Stratify for Jira

Welcome to the official documentation for Stratify for Jira! 🎉

Stratify for Jira is a Forge app for Jira Cloud. It lets you plan work on a nested Gantt, with a customer-defined hierarchy, without writing to Jira until the planner syncs.

The UI follows the user language in Jira (Spanish (Spain) and English (United States)). The Parent Element field key and stored values do not change when the user switches language.

Stratify for Jira is a paid app. Without an active license, Command Center, the hierarchy panel, the Parent Element field, and the Gantt are blocked. This guide installs the app with the Forge link. See the Installation Guide for licensing and the steps after install.

Install Stratify for Jira

Who is this app for?

Target audience

Stratify for Jira is built for PMOs, project managers, and portfolio owners who need a multi-project Gantt, a hierarchy that matches their operating model (OKRs, SAFe, Initiative → Epic → Story, or another site-specific tree), and date scenarios that do not touch Jira until the plan is confirmed.

Capabilities in version 1.1.0 (Forge 3.0.0)

Capability	Benefit
Configurable hierarchy	Parent Element field and Parent → Children rules defined by the administrator.
Multi-project Gantt	One JQL feeds bars from several projects, according to the user’s permissions.
Saved plans	Keeps the JQL and view so you can reopen the same plan.
Sandbox (Draft)	Moving or stretching dates lives in draft until you click Sync. Each plan’s draft is restored after a reload.
Bulk sync	Sends every draft change to Jira, with a per-issue success or failure summary.
Estimate roll-up	Each parent shows the sum of Story Points or hours of visible children.
Optional date roll-up	A toggle extends the parent in Draft when a child slips past its finish date.
Blocks dependencies	Blocks / is blocked by arrows and visual alerts for date conflicts.
Marketplace license	Paid app. Without an active license, features are blocked.
Language and branding	UI in es-ES / en-US and product logo.

Not in 1.1.0: team capacity, budget, and real objectives. Those surfaces are not shown in the app; they belong to a later phase.

How the pieces fit together

1. The administrator associates Parent Element with the relevant issue types and screens, then saves Parent → Children rules.
2. The planner opens the Gantt, enters a JQL, and optionally saves a plan.
3. Bars nest according to the hierarchy and the Parent Element field.
4. Date changes live in Draft. Jira is not updated until Sync.
5. Roll-ups and Blocks arrows show effort and conflicts without blocking the draft.

Next step: Installation Guide.