Overview
Hierarchies for Jira has been rebuilt on the Atlassian Forge platform, replacing the previous Connect version. This guide covers what changes and what to expect during the upgrade.
What’s new
The Forge version is functionally equivalent to the Connect version with these improvements:
- Native performance — Runs on Atlassian’s infrastructure, no external hosting dependencies
- Better reliability — No dependency on third-party servers
- Improved admin page — Cleaner, more responsive interface for configuring hierarchies
- Custom aggregators — Define your own computed fields using Jira Expressions
- Queue-based sync — Reliable background synchronization for large instances
All existing features — hierarchy tree view, aggregation, multi-level configurations — continue to work. No features have been removed.
During migration
The upgrade happens through the Atlassian Marketplace. When the new version is installed, Atlassian automatically replaces the previous Connect app with the Forge version.
Your existing hierarchy configurations and issue relationships are preserved. The app migrates your data automatically on first launch.
After migration
Once the upgrade is complete, verify your setup:
- Go to the admin page and confirm your hierarchy configurations are present
- Run a full sync to rebuild all hierarchy properties
- Open the Tree panel on a project and confirm issues display correctly
- Verify aggregated fields are computing as expected
If any hierarchies didn’t migrate, you can recreate them following the Configuration guide.
What stays the same
- All Jira issue data — issues, links, fields — remain unchanged
- Your existing hierarchy structures are preserved
- The tree view and aggregation work the same way
- The app appears in the same location in the Jira UI
Support
If you encounter issues during or after migration, contact us through the customer service portal.