Containers
What are Containers?
Similar to Jira epics, Epic Sum Up containers can be parents of other issues.
What can they be used for?
Epic Sum Up containers allow you to create flexible structures. Containers are not bound to a specific issue type hierarchy, and they can be stacked to any height.
How can you use them?
Containers vs Epics vs Jira Advanced Roadmaps
We need to briefly cover what epics and Jira Advanced Roadmaps are, here, before we continue.
Epics are a single deliverable/goal/project, represented by folders within a project hierarchy. Within an epic, a project manager can create different kinds of issues.
Advanced Roadmaps, meanwhile, are a planning tool that can be used across projects. Typically Advanced Roadmaps are used to create plans that span multiple teams and/or entire organizations. Advanced Roadmaps allow more control over issues, issue schemes, etc.
Epic Sum Up containers are a structural element, similar to epics. However, ESU containers offer more flexibility & features, compared to epics and Advanced Roadmaps.
You can stack child issues into containers simultaneously while you stack containers within containers.
Unlike Advanced Roadmaps, in containers stacking is flexible and not limited by issue scheme. With ESU containers you can stack other containers or issues to any height.
Container Links
Issue links are used to link containers to other containers and child issues. Which link types are used for this is defined by the administrator in the global configuration.
Please note that only issue types defined as containers in the global configuration can become a container. And containers cannot be linked to subtasks.
Let’s take a look at how to link containers, using the example links: Container Parent and Container Child.
The link name refers to what the linked issue is in relation to the issue you are viewing. So if you are using the container parent link, the linked issue will become a parent of the issue you are viewing. And if you are using the container child link, the linked issue will become the child of the issue you are viewing.
The logic and order of the links is up to your administrator to decide.
To see the complete structure you have built, open up the Detail View Editor by clicking on any progress bar.
Best Practices
Note that we have built the container feature only to extend - not replace - the building of Jira hierarchies.
Extending Jira hierarchies can look like:
Grouping different Advanced Roadmaps hierarchies into one
linking in Advanced Roadmaps unused issue types directly to the top level container
link issues that don’t have an epic or parent link to a container
All of this flexible hierarchy building will be visible in the Detail View Editor where you can easily create new issues, summarise and edit values, filter, export and more - all in one place.
Feature differences
Due to the technically different environments of the Cloud and Data Center/Server, we are not able to deliver the container feature in the same way for both. Which is the reason we are using issue links instead of container links in the Cloud.
The most important thing for us was to enable you to build flexible structures in the Cloud. And that is now possible.
If you have any questions or feedback you would like to share with us, contact our support team.
Which means it is also easier for you to migrate from On-premise to Cloud. We are still working on the support of the migration assistant but you can read how to manually migrate Epic Sum Up on this page.
In terms of other container features: the issues in container list is still only available on Server and Data Center.
Known Limitations
As stated above, there are some known limitations due to the technical differences between Cloud and Data Center. Below we have compiled a list of the most common ones.
Containers are only an extension for building Jira hierarchies.Meaning that if an issue has both an issue and an epic or parent link, Epic Sum Up will prioritise the Jira links.
Jira on the other hand only takes its own hierarchies into account. Which is why containers should not be used below epics, since issues below the container will not be visible in list views on agile boards.
If you use containers together with Advanced Roadmaps, this will not be reflected in the Advanced Roadmaps plans. As Jira only recognises its own hierarchies.
With issue links, circle connections can be built. While we made sure this cannot cause issues or that issues appear twice in the Detail View Editor, you may get different structures depending on the issue you are opening the Detail View Editor from.
If you have any questions or suggestions about containers, please contact our support team. Your feedback - especially about a major feature like this one - is very valuable for us.