[MGNLUI-94] As a user I can sort by status (and other semantically richer columns) to get the changed content Created: 25/Oct/12 Updated: 13/Mar/20 Resolved: 13/Mar/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | tree/list, workbench |
| Affects Version/s: | 5.0 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 1 |
| Labels: | list, sorting, tree, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Description |
|
Currently, the "Status" column in a list of pages is not sortable. We should add sort support for other value types like this one as well. I'd expect this to be more of an infrastructural task in that we ensure that specific fields of content types can be sortable and that this property is taken through to the UI. In this particular case, a sort order would return the published, then changes, then unpublished pages, if sorted descendingly. |