[
http://jira.magnolia-cms.com/browse/MGNLUI-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Weder updated MGNLUI-97:
--------------------------------
Summary: Add support to group rows by type to ANY list (was: Add
support to group rows by type to a list)
Labels: ux grouping (was: )
Fix Version/s: 5.0 Alpha1
Affects Version/s: 5.0 Alpha1 S7
Priority: Critical (was: Neutral)
Description:
Currently, on the messages list in Pulse supports grouping its entries by type.
*Grouping by a specific attribute should be available to any list*, however.
Obviously, not all columns in a list actually make sense to act as grouping
attributes. Which ones are has to be decided on an app and view-by-view basis
and thus should be configurable. The infrastructural support for grouping shall
be available to all list instances.
As an example, in the list of pages in the Pages app, both the "Status" and the
"Template" columns are very rewarding candidates to group the list by. We'll
thus offer a "Group by" option in the view options area, which offers both a
checkbox to turn it on and off as well as a small drop down menu to select
either one of these two attributes.
The goal of this task is to ensure that:
- grouping attributes can be configured on a list-by-list basis
- a single or multiple such attributes can be chosen from (manually determined,
when you create the list)
- the corresponding group controls are available in the view options as well.
> Add support to group rows by type to ANY list
> ---------------------------------------------
>
> Key: MGNLUI-97
> URL: http://jira.magnolia-cms.com/browse/MGNLUI-97
> Project: Magnolia UI
> Issue Type: Sub-task
> Security Level: Public
> Affects Versions: 5.0 Alpha1 S7
> Reporter: Andreas Weder
> Priority: Critical
> Fix For: 5.0 Alpha1
>
>
> Currently, on the messages list in Pulse supports grouping its entries by
> type. *Grouping by a specific attribute should be available to any list*,
> however.
> Obviously, not all columns in a list actually make sense to act as grouping
> attributes. Which ones are has to be decided on an app and view-by-view basis
> and thus should be configurable. The infrastructural support for grouping
> shall be available to all list instances.
> As an example, in the list of pages in the Pages app, both the "Status" and
> the "Template" columns are very rewarding candidates to group the list by.
> We'll thus offer a "Group by" option in the view options area, which offers
> both a checkbox to turn it on and off as well as a small drop down menu to
> select either one of these two attributes.
> The goal of this task is to ensure that:
> - grouping attributes can be configured on a list-by-list basis
> - a single or multiple such attributes can be chosen from (manually
> determined, when you create the list)
> - the corresponding group controls are available in the view options as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
