Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Issues appearing in the Unassigned swimlane when Grouping by...

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.

 

TST7-35_duplicated.png

 

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?

 

TST7_SCRUM_-_Assignee.png

 

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.

 

TST7-35_epic_to_epic.png

 

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.

1 comment

Mohammed Amine Community Leader Jun 09, 2021

Good information

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

243 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you