Container - Build hierarchies without Jira limits, no matter if you’re on Jira Standard or Premium

Your Jira hierarchy has rules. ESU Containers have considerably fewer. 👀 Need more flexibility in how you structure work in Jira? Containers in ESU (Enterprise Summaries) let you build and extend hierarchies beyond the usual Jira restrictions. Without turning your setup into complete anarchy. In this video, Johanna from our APTIS team covers both sides of ESU Containers: how they work AND how to configure them from scratch. ✨ What you’ll learn: ✔️ What ESU Containers are and when to use them ✔️ How Containers differ from standard Jira hierarchies ✔️ How to create flexible, multi-level hierarchies ✔️ How the Container Link connects work items ✔️ How to view your entire hierarchy in the Container List ✔️ How to save different hierarchy views as layouts ✔️ How Containers can extend existing Jira hierarchies ✔️ Which hierarchy setups we recommend avoiding ✔️ How to configure Container work types ✔️ How to use JQL to control the Container Link selection ✔️ How to add the Container Link field to your Jira screens 🪄 Why Containers? Standard Jira hierarchies are great - until your actual project structure doesn’t quite fit into them. With ESU Containers, you can add additional hierarchy levels, group existing Jira hierarchies and structure work more flexibly while still keeping the bigger picture visible. And on top of that, the setup is MUCH quicker than this list makes it sound. 😄 Perfect for Jira Admins, Project Managers and teams looking for more flexibility in Jira hierarchy management, portfolio structures and work item organization. 🪄One important tip: Containers work best when they extend Jira hierarchies rather than replace them. Johanna explains exactly where to use them and where you probably shouldn’t. 👇 If this video helped you: 👍 Give it a thumbs up 👀 Subscribe for more Jira tips, ESU tutorials & use cases 💬 Let us know which ESU feature or Jira myth we should break down next