Custom Hierarchy Levels in Jira Without Premium
Jira Standard caps the issue-type hierarchy at Epic. To add a level above — Initiative, Theme, Program — Jira itself wants you to upgrade to Premium. You don't have to. Three Marketplace apps (Structure, BigPicture, Foundation) layer custom hierarchy outside Jira's schema, on Standard tier, for a fraction of what Premium costs across a whole install.
Why can't Standard-tier Jira add custom hierarchy levels?
In Jira's data model, every issue has an issue type, and every issue type sits at a specific hierarchy level. Out of the box, Jira ships three levels: subtask at the bottom, standard issue types (Story, Task, Bug) in the middle, and Epic on top. That's it. There is no “add level above Epic” button on Standard tier.
The issue-type hierarchy configuration screen — where you'd add Initiative or Theme — is gated behind Jira Premium. See the tier comparison for the current delta. That's not a technical limit of the Jira schema; it's a packaging decision. The schema could clearly support it (Premium uses the same underlying database), but Atlassian reserves the configuration screen for the higher tier.
Which means there are really only two paths for a Standard-tier team that needs an Initiative level: upgrade every Jira seat to Premium, or install a Marketplace app that adds the level on top of Jira without touching the native schema. For most organizations the second option is dramatically cheaper, because Jira Premium prices per user — so the delta compounds across every seat, including the ones that never touch the hierarchy.
What does “custom hierarchy level” actually mean to these apps?
The three apps all approach this the same way conceptually: they create a parallel tree, outside Jira's native issue-type hierarchy, that references real Jira issues at the leaves and adds custom parent containers above them. The parent containers (Initiative, Theme, Program, whatever you name them) live only inside the app's data layer — Jira itself still sees Epics and Stories as the top of the tree.
This matters in two ways. First, it means you can add as many levels as you want without waiting for Atlassian to bless it — the apps don't touch Jira's schema. Second, it means anyone querying Jira directly (BI tools hitting the REST API, or integrations written against Jira's native hierarchy) won't see the custom levels unless they also integrate with the app's data layer. Usually that's fine — most reporting happens inside the app itself — but it's worth knowing.
Option 1 — Structure (Tempo): most mature, high price
Structure by Tempo is the oldest and best-known hierarchy app on the Marketplace, with over a decade of development and the largest install base. It pre-dates the Epic/Initiative hierarchy discussion by years — Structure organizations built custom multi-level trees long before Jira Premium existed as a concept.
What you get: arbitrary-depth trees, cross-project rollup, a powerful rule engine called Structure Automation for keeping trees in sync with JQL, manual and automated tree construction, and integrations with other Tempo products (Timesheets, Planner). Structure is the most feature-complete option in the category.
The cost profile is the highest of the three. Structure's per-user pricing is the tier leader, and if you also want Gantt visualization you pay separately for Structure.Gantt, which is a standalone Marketplace listing stacked on top of Structure's own subscription. For organizations already invested in the Tempo ecosystem the integration value offsets the cost; for a team just needing an Initiative level, it's usually overkill.
Option 2 — BigPicture (Appfire): PMO-oriented
BigPicture by Appfire positions itself as a full PMO suite, not just a hierarchy tool. Beyond custom levels it bundles portfolio management, program management, resource management with capacity histograms and auto-leveling, risk management, and a Gantt module. It's the deepest option for organizations that want hierarchy alongside formal PPM/PMO practices.
The hierarchy itself supports up to 12 configurable levels. BigPicture maps custom levels to concepts from established portfolio-management frameworks (SAFe Portfolio, SAFe LPM, PMI PMBOK), which is useful if your organization runs one of those frameworks formally.
Price-wise BigPicture sits in the middle of the three — less than Structure + Structure.Gantt combined, more than Foundation. The tradeoff is complexity: BigPicture is modular, and turning on modules you don't need creates a steeper learning curve than a lighter-weight tool would. Teams that actually use the PMO features get their money's worth; teams that just need custom hierarchy often find BigPicture more tool than they need.
Option 3 — Foundation: Forge-native, lowest price, simpler data model
Foundation is the newest entrant and takes a deliberately different architectural approach. It's built on Atlassian Forge (the platform Atlassian is standardizing on post-Connect), runs inside Jira, and stores its hierarchy data in Forge SQL colocated with the Jira tenant.
What Foundation adds above Epic is called a Flex Item — a custom parent that lives in a Foundation Lens but not in Jira's native schema. You can nest Flex Items arbitrarily: Initiative > Theme > Program, or whatever tree depth makes sense for your org. At the leaves, Flex Items reference real Jira issues via the issue cache. Foundation also supports a 1,000-issue Lens cap in the MVP — adequate for most portfolio views, modest compared to Structure's effective limits.
Price-wise Foundation sits below Structure and below Structure + Structure.Gantt combined. The free tier covers teams up to 10 users, so a small org exploring hierarchy can try the real product at zero cost. Foundation ships its Gantt view inside the same subscription — not a separate line item — which lands the bundled price below alternatives that charge separately for Gantt capability. See the Foundation vs BigPicture and Foundation vs Structure pages for detailed head-to-head breakdowns.
Foundation's tradeoff is maturity. Structure has a decade of production hardening; BigPicture has a broader feature footprint. Foundation is newer, scoped intentionally for the most common use cases, and priced accordingly. For budget-conscious Standard-tier orgs that need hierarchy + Gantt and don't need enterprise PMO machinery, it's usually the best-fit option.
Side-by-side comparison
| App | Hierarchy depth | Cross-project | Relative per-user price | Forge-native | Free tier |
|---|---|---|---|---|---|
| Structure (Tempo) | Effectively unlimited | Yes | Highest; Gantt sold separately | No (Connect-based) | Up to 10 users (free for small teams) |
| BigPicture (Appfire) | Up to 12 levels | Yes | Middle; Gantt bundled in suite | No (Connect-based) | Up to 10 users |
| Foundation | Arbitrary depth; 1,000 issues per Lens (MVP) | Yes | Lowest; Gantt bundled | Yes (Forge-native) | Up to 10 users |
Forge-native matters for three reasons in 2026: data stays inside the Atlassian trust boundary (no third-party cloud hops), Atlassian is actively migrating their own ecosystem to Forge, and Forge apps get Atlassian-managed infrastructure rather than self-hosting. Structure and BigPicture are both Connect-based (the older model); Foundation is Forge-native.
When is upgrading to Premium actually the right answer?
A Marketplace app is usually cheaper than upgrading to Premium for the hierarchy alone, but Premium includes more than just custom hierarchy levels. If your org already wants multiple Premium-gated features — Advanced Roadmaps / Plans, sandbox environment, release tracks, guaranteed uptime SLA, 24/7 Premium support, unlimited storage — then the Premium math changes.
The decision comes down to which features you'll actually use. If the only Premium feature you need is “add a level above Epic,” a hierarchy app is almost always cheaper, especially at scale. If you'd get value from Plans, sandboxes, and the Premium-tier SLAs in addition to hierarchy, upgrade and skip the app.
A hybrid pattern that works well for larger orgs: keep Jira on Standard, add a hierarchy app for the portfolio team (Initiative level and up), and reserve Premium for specific projects or Jira sites that need the other Premium-only features. Most Marketplace hierarchy apps charge per-user based on your Jira install size, so consolidating portfolio users onto a dedicated site can help contain app cost.
What happens if you later DO upgrade to Premium?
Upgrading from Standard to Premium doesn't break anything you built in Structure, BigPicture, or Foundation. The apps continue to work post-upgrade because they never depended on Premium in the first place — they built hierarchy in their own data layer, outside Jira's schema.
What doesn't happen automatically: your custom hierarchy levels don't merge into Jira's native Premium hierarchy. Those are two separate trees. If you want to consolidate them, you'd need to: create matching issue types in Jira Premium (Initiative, Theme, etc.), create real Jira issues for each custom parent the app owns, and re-parent the underlying Epics to the new Jira Initiatives. This is a one-time manual project. Most teams don't bother.
Instead, most teams keep running the hierarchy app post-upgrade for the same reason they installed it in the first place: the app's views, rollups, cross-project aggregations, Gantt capability, and configurability go well beyond what Jira Premium's native hierarchy offers on its own. Premium gives you the configuration screen; the apps give you the entire portfolio-management surface on top.
Where to go next
- Jira hierarchy beyond Epic — the full pillar guide
- How to add Initiatives above Epic in Jira
- Jira Plans vs Structure vs Foundation for hierarchy
- What is a Lens? Foundation's cross-project portfolio view
Frequently asked questions
Can I add an Initiative level above Epic in Jira Standard without paying for Premium?
Not through Jira itself — the issue-type hierarchy configuration screen is a Premium-only feature. You can, however, get the same result using a Marketplace app: Structure, BigPicture, and Foundation all layer custom hierarchy on top of Jira Standard without requiring a tier upgrade. You pay per user for the app instead of paying per user for Premium across your whole Jira install.
If I use a hierarchy app, do my custom levels show up inside Jira issues or only inside the app?
Only inside the app. Structure, BigPicture, and Foundation all store their extra hierarchy outside Jira's native issue-type schema — Jira itself still sees the underlying issues as Epics, Stories, and Tasks. The custom parents (Initiatives, Themes, Programs) exist only when you open the app's view. That's usually fine, but if your organization reports on hierarchy from BI tools hitting the Jira API directly, plan for that.
What's the cheapest way to get an Initiative → Epic → Story hierarchy in Jira?
If your org is under 10 users, Foundation's free tier covers it at zero cost. Above 10 users, compare the per-user cost of a hierarchy app against the per-user delta between your current Jira tier and Premium. For most organizations in the 25–500 user range, a per-user Marketplace hierarchy app is meaningfully cheaper than upgrading every Jira seat to Premium, because Premium's price delta compounds across every user whether they touch the hierarchy or not.
Will custom hierarchy levels survive if I later upgrade to Jira Premium?
The underlying issues always survive — they live in Jira. What changes is where the hierarchy relationships live. Structure, BigPicture, and Foundation each store parent-child relationships in their own data layer, so those relationships stay inside the app after a Premium upgrade. If you want to migrate them into Jira's native Premium hierarchy, you'd need to create matching Jira issue types and re-parent the issues, which is a manual one-time project. Most teams keep running the app post-upgrade because the app's views, rollups, and Gantt capabilities go beyond what Premium's native hierarchy offers.
How deep can each app's custom hierarchy go?
Structure supports effectively unlimited depth — the limit is rendering performance, not a hard cap. BigPicture supports up to 12 levels depending on your configuration and module. Foundation's MVP supports arbitrary depth up to 1,000 issues per Lens, with Flex Items allowing custom parent levels anywhere in the tree. For most portfolio use cases three to five levels is the practical sweet spot; deeper trees become hard to read regardless of tool.
Does a hierarchy app work with Jira Standard or do I need at least Jira Software?
All three apps work with Jira Software Standard. Jira Software (any tier) is required — the apps read issue data from Jira, so you need Jira Software for the underlying project. They do not require Jira Premium or Jira Enterprise. Jira Work Management has partial compatibility depending on the app; check each Marketplace listing for current compatibility before purchase.