Content
View differences
Updated by Max Mutzge over 5 years ago
As a user of the "group by" feature
I want to see a group "not set" or "none", too
so that I get a complete and not misleading overview over my work packages.
### Current behaviour
The "group by" feature works like a filter that users don't know about and that can't be removed by changing the filter settings.
Examples:
\-when grouping by assignee the fact that all the work packages without an assignee are not shown is misleading - it looks like there are fewer work packages than there rally are
\-the "low hanging fruits" [query](https://community.openproject.com/projects/openproject/work_packages?query_id=903) looks like - judging by the filters set - that there were only 9 specified or confirmed work packages in the product backlog. That's because all work packages without a set code layer are not shown.
### Acceptance criteria
* When using the "group by" feature there's a separate group shown.
* It's called something like "not set" or "none".
* It includes all the work packages for which the attribute that the user groups by is empty or not set.
* It behaves like the other groups.
* Using "group by" doesn't lead to the exclusion of work packages from the work package list any more
I want to see a group "not set" or "none", too
so that I get a complete and not misleading overview over my work packages.
### Current behaviour
The "group by" feature works like a filter that users don't know about and that can't be removed by changing the filter settings.
Examples:
\-when grouping by assignee the fact that all the work packages without an assignee are not shown is misleading - it looks like there are fewer work packages than there rally are
\-the "low hanging fruits" [query](https://community.openproject.com/projects/openproject/work_packages?query_id=903) looks like - judging by the filters set - that there were only 9 specified or confirmed work packages in the product backlog. That's because all work packages without a set code layer are not shown.
### Acceptance criteria
* When using the "group by" feature there's a separate group shown.
* It's called something like "not set" or "none".
* It includes all the work packages for which the attribute that the user groups by is empty or not set.
* It behaves like the other groups.
* Using "group by" doesn't lead to the exclusion of work packages from the work package list any more