[MGNLUI-5730] Cannot filter by status in list view Created: 12/Mar/20  Updated: 16/Mar/20  Resolved: 16/Mar/20

Status: Closed
Project: Magnolia UI
Component/s: tree/list
Affects Version/s: 6.2
Fix Version/s: 6.2

Type: Bug Priority: Neutral
Reporter: Canh Nguyen Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.25d
Time Spent: 2h 40m
Original Estimate: Not Specified

Issue Links:
relation
supersession
supersedes MGNLUI-94 As a user I can sort by status (and o... Closed
supersedes MGNLUI-3480 Sorting in content apps only works fo... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: UI Framework 19

 Description   

Step to reproduce:

  1. Open Pages app
  2. Click List view
  3. Select a status in Status column header

Please check the video in this link https://drive.google.com/file/d/1g6iNGaPX5D4sJps4iDDHx1ND-uUk1PTa/view?usp=sharing

Furthermore, the URL still displays tree instead of list (I suppose it should be "list").



 Comments   
Comment by Richard Gange [ 12/Mar/20 ]

It's more than just the status column that needs to be looked at and it's not specific to the pages app. See MGNLUI-3480.

Comment by Roman Kovařík [ 13/Mar/20 ]

rgange This is an issue in new UI framework. The ticket you mentioned was reported agains the old framework.

Comment by Richard Gange [ 13/Mar/20 ]

rkovarik thanks for that clarification but don't you think the proposed solution by Cedric still applies? I think the description here really narrows the scope. Let's create a configuration that allows users to define the logic of how the column should display it's contents.

Then we create the an implementation for the status column. Really it's 2 tickets.

Comment by Roman Kovařík [ 13/Mar/20 ]

Just noticed that MGNLUI-3480 speaks about sorting whereas this ticket is about filtering (it's not possible to filter by properties in the old framework).
For the record, the new framework datasources can filter its content so you can provide your own datasource with a custom filtering logic (e.g. the out-of-the-box JCR datasource has a custom logic to filter by activation status or node name even though these are not JCR properties)

Comment by Richard Gange [ 13/Mar/20 ]

Gotcha. So we will have the flexible option. Perfect!

Generated at Mon Feb 12 09:29:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.