nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Timeline has unassigned if grouped by team

Johan Janssens

I was looking into creating a Timeline for our teams progess and when grouped by Team i have all issues grouped in teams as requested, but I also see all the issues in the "Unassigned" Team

the first screenshot shows the Dev team:

Schermafbeelding 2025-03-11 145955.png

Below the Dev team there is the "Unassigned" section

Schermafbeelding 2025-03-11 150017.png

Eventough, the stories are assigned to dev and team and sprint, they still appear in the unassgned catory & the dev team, i don't know what else to assign them too.

Comments

Walter Buggenhout

Hi @Johan Janssens and welcome to the Community!

Could it be because your epics and initiative level issues are not assigned to a team? I can see from your screenshots that they are rolling up team assignment from the issues below (which is fine, by the way - but they do not have an assigned team).

In your grouped by team view, you could apply a filter on hierarchy level, so the levels above stories are not displayed. There is a good chance that your unassigned issues may be gone then.

Hope this helps!

Johan Janssens

I initially thought it was fixed. however it's not the case, Yes the unnassgned team is gone now, BUT now it will add all the rolled up estimation values of the epics to the teams.

Walter Buggenhout

That looks like a different problem then 😛 ...

It is definitely so that when you start grouping items in a view, some of the behaviour from the default basic view (like roll-ups, duplicate items in groups, ...) may become confusing.

It is possible to create different views for different purposes, so you can eliminate the unwanted behaviour in one view and - oppositely - apply it in other views. If you display the full hierarchy of your WBS, rollup makes sense, while it may not be useful if you only display one hierarchy level. Views can be saved, so you can access them with a single click from the dropdown with saved views.

Hopefully, that will allow you to create bespoke visualisations for the specific use cases you have.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

portfolio-for-jira

portfolio-for-jira-cloud