Jira Evolution: Universal Fractal Governance – Decoupling Issue Hierarchy for SAFe & Portfolio Scale

[THIERRY ALEXANDRE]

Hello Atlassian Community,

As a Jira Administrator managing complex environments, I often observe a friction point between Agile Theory (SAFe) and Tooling Reality. While Jira excels at the Team (Level 0) and often the Portfolio (Level 2) layers, there is a persistent 'Execution Gap' at the Program/Feature level (Level 1).

I am sharing a formal Evolution Request for what I call Universal Fractal Governance Support. The goal is to allow Jira to treat all hierarchy levels as first-class 'executable' citizens on boards.

I believe this would significantly unlock Program Increment (PI) tracking for thousands of organizations. I would love to hear your thoughts on this approach and invite the Atlassian Product teams to consider the business value of this decoupling."

--------------------------------------------------------------

Jira Evolution Request: Universal Fractal Governance Support

Subject: Decoupling Issue Hierarchy from UI Rendering to Support Scaled Agile (SAFe)

1. Executive Summary

The modern DSI (Information Systems Department) requires a Fractal Governance model where work is committed and "timestamped" at every level. While Jira supports this for Level 0 (Stories) and Level 2 (Initiatives), it imposes a hard-coded UI restriction on Level 1 (Epics), preventing them from being managed as executable "cards" on Scrum Boards. We request the ability to treat Level 1 issues as standard work units to support Program Increment (PI) tracking.

2. Key Terminology Alignment (SAFe)

To ensure international coherence, the following terms are used:

• Level 2 (Initiative/Capability): Managed via Strategic Portfolio Reviews 
• Level 1 (Feature/Epic): Managed via Program Increments (PI).
• Level 0 (Story): Managed via Team Sprints.

3. The Problem: The "Level 1" Execution Gap

Currently, Jira Software forces Level 1 issues into the "Epic Panel" sidebar.

• The Inconsistency: Level 2 issues can be rendered as cards and assigned to Sprints (for Portfolio Reviews). Level 0 issues do the same for teams.
• The Blockage: Level 1 (the "Feature" layer in SAFe) cannot be managed as a card. This prevents Program Managers from "stamping" Features into a PI Sprint and tracking their flow through columns (e.g., Funnel > Analysis > Backlog > Implementation).

4. Proposed Solution: Polymorphic Board Rendering

We request a board-level setting: "Enable Level 1 Issues as Standard Cards."

• Functionality: When enabled, the "Epic Panel" is bypassed. Level 1 issues appear in the Backlog and can be dragged into Sprints.
• Fractal Synchronization: This allows a single Sprint field to act as a universal temporal anchor:
  • Sprint = "ROP 26.1" (Strategic Portfolio Review)
  • Sprint = "PI 26.1" (Program Increment)
  • Sprint = "S 1.1" (Team Delivery)

5. Business Value & Predictability

• Unified Traceability: Enables JQL queries to return the entire value chain for a specific period.
• Program Predictability: Allows for "Program Velocity" reporting (Features per PI) using native Jira Sprint gadgets.
• SAFe Compliance: Directly supports the Architectural Runway and Feature Delivery tracking required by Scaled Agile frameworks.

[THIERRY ALEXANDRE]

Thank you John, I ll do it right away.  I am interested however to see if this make sense for the Community. 

[John Funk]

Hi Thierry - Welcome to the Atlassian Community!

This is an end user community and not typically monitored by Atlassian product personnel. You need to open a support/feature request to make those wishes known. 

https://support.atlassian.com/contact/#/