"Unassigned" top-level group in backlog view?
I'm looking at plan items in a backlog format grouped by category.
All categories appear to be children of a top-level heading called "Unassigned".
Why is that? What does it mean?
Grouping by anything else gives the expected result, but grouping by category always adds this extra redundant/confusing level.
All categories appear to be children of a top-level heading called "Unassigned".
Why is that? What does it mean?
Grouping by anything else gives the expected result, but grouping by category always adds this extra redundant/confusing level.
One answer
On 12/9/09 4:53 PM, jneau wrote:
The WorkItem component lets you create multiple categories and associate
teams with it. Categories shall be used to populate the Filed Against
field. When categories are defined and associated with a team, the plan
will allow you to group by them.
See http://jazz.net/library/article/131 for more details.
--
Cheers, Johannes
Agile Planning Team
I'm looking at plan items in a backlog format grouped by category.
All categories appear to be children of a top-level heading called
"Unassigned".
Why is that? What does it mean?
Grouping by anything else gives the expected result, but grouping by
category always adds this extra redundant/confusing level.
The WorkItem component lets you create multiple categories and associate
teams with it. Categories shall be used to populate the Filed Against
field. When categories are defined and associated with a team, the plan
will allow you to group by them.
See http://jazz.net/library/article/131 for more details.
--
Cheers, Johannes
Agile Planning Team