Rank Cascading for Jira - closing a gap that's been open since 2018

[#1]

Quick demo showing how Rank Cascading for Jira works in practice.

This has been an open gap since at least 2018 (community) and 2022 (JSWCLOUD-23112). The only workarounds people have found involve custom REST API scripts running on a schedule - not a real-time sync. I've been there too, having built exactly that kind of script in a Data Center setup years ago.

The setup in this demo:

Portfolio Board	Team Board
the single source of truth for epic prioritization	showing the current rank order of child issues

When epic ranks change at the portfolio level, the Team Board is immediately out of sync - which is the everyday problem this app solves.

The demo covers:

->Cascade configuration
->Reordering epics on the Portfolio Board
->Cascade Preview - see the inherited rank distribution before applying anything
->Sync - one click to push the updated ranks down to all child issues

The Team Board then reflects exactly the portfolio priority order. No manual re-ranking across teams.

👉 Rank Cascading for Jira - Demo

Available on the Atlassian Marketplace

Enjoy the freedom of having one rank to rule them all

[C_ Faysal_CFcon_]

Update: What's new since v4.0.0

• Native Rank Sync - calculated ranks can now be synced directly to Jira's native board order. Team boards stay aligned with portfolio priorities after every sync.
• 3-Level Hierarchy - rank inheritance across Epic, Story, and Sub-task with unique sub-ranks per level.
• Full JQL Swimlane Support - swimlane grouping now supports the full Jira query language including AND, OR, IN, and custom fields.
• JQL Validator - test your JQL directly in the cascade config before saving.
• Cross-Board UX - drag-to-reorder boards, board statistics in preview, source board indicator per issue, and proportional merge mode for mixed board sizes.
• Enterprise-grade rate limiting - all API paths handle Atlassian rate limits with automatic retry and backoff.