The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
@Walter Buggenhout the item "Hierarchy issue limit" does it mean about EPICs? I didn't get the reference about "ISSUE LIMIT" and "HIERARCHY ISSUE LIMIT".
It's clear and no questions about "Team limit" and "project limit".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Epics are indeed one level of the hierarchy. A traditional hierarchy in advanced roadmaps is set up like this:
Initiatives at the highest level
Epics at the level below
Task, Story, Bug, ... at the level below
Sub-tasks at the lowest level
Each of those is a hierarchy level. And so you can have a maximum of 2.000 issues at each level.
As the hierarchy will be more or less like a pyramid (fewer items as you move up to the higher levels), it is a good idea to assume you can have 2.000 Task, Story, ... issues in your plan and probably fewer epics, initiatives.
The absolute issue limit really is the total number of issues you can have in your plan, regardless of the level they are at.
Teams live on a separate tab in the roadmap. Most likely, you will have 1 team for each board or project you pull into your plan. You can have up to 50 of those in a single plan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.