[MGNLUI-7070] Filtering by publication status doesn't work in app generated from content types Created: 22/Mar/22  Updated: 27/Apr/22  Resolved: 15/Apr/22

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.17
Fix Version/s: 6.2.19

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
Cloners
clones CONTEDIT-475 Filtering by publication status remov... Closed
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Support
Sprint: DevX 8
Story Points: 2
Team: DeveloperX

 Description   

Steps to reproduce

  1. Login to demo org
  2. Navigate to the Tours App
  3. Change status from "All" to any other publication status
  4. Notice no content is returned

Screenshot attached

Expected results

Content is returned when filtering by publication status

Actual results

Content is not returned when filtering by publication status

Workaround

Rename status column in the browser template to jcrPublishingStatus.

Development notes

The status column definition could throw an IllegalStateException from public init() to produce a definition app error if the column has a different name.

 



 Comments   
Comment by Roman Kovařík [ 22/Mar/22 ]

Discovery:

  • the cause described in the workaround section
  • ticket cloned from original ticket and moved to UI project
  • assigned to DeveloperX (according to the domain app)
Generated at Mon Feb 12 09:42:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.