You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When viewing work in Advanced Roadmaps, the View settings menu lets you customize how issues and related information are displayed on your timeline.
By using the Group by Assignee, Release, Sprint or Team, each group will be allocated a swimlane containing assigned issues. Any unassigned issues will be in the Unassigned swimlane.
This grouping is done with respect to the hierarchy range selected, this is to say if you're using a hierarchy range above 1 level, then you can expect to find issues duplicated on both the assigned and Unassigned swimlanes.
From the example above where we're using the Group by Assignee option, we see issue TST7-35 appearing twice, indicating that it is both assigned to Belto but also Unassigned, now why is that?
If we remove the Group by view and just view the full hierarchy of issue TST7-35 we will see that this is an Epic issue type that has child Stories. While the Epic parent itself is assigned to Belto as well as some of its child Stories, there are a couple of others that are unassigned.
The hierarchy range selected here is Epic to Sub-Task which means that the Plan has an obligation to display issue types of these levels in the hierarchy, regardless of their assignment.
Taking these 2 factors into account, when I Group by Assignee the Plan has an obligation to group all issues assigned to Belto to the assigned column, but it also has another obligation to display the entire hierarchy of the Epic and since the child Stories are nested under the Epic, the Epic will have to also be displayed under the Unassigned swimlane due to its children.
Just like what's shown above, to avoid the duplicated views, you simply need to restrict the hierarchy range to one particular level this way it doesn't have any other obligation besides grouping the issues to their assigned columns.