[MGNLUI-6686] JcrObservation reacts on irrelevant changes Created: 04/May/21  Updated: 16/Jul/21  Resolved: 06/May/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.8
Fix Version/s: 6.2.9

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

Issue Links:
Relates
relates to MGNLWORKFLOW-403 Recursive publication crashed instance Closed
relation
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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Epic Link: Grid performance
Sprint: Maintenance 56
Story Points: 2

 Description   

Steps to reproduce

  1.  MGNLWORKFLOW-403

Expected results

JCR Datasource reacts only on changes in visible items.

Actual results

JCR Datasource reacts on changes in sub nodes of visible items, probably even on system versioning nodes.

Workaround

N/A

Development notes

Observation might use JCR out of the box setting like

  • root path
  • node types


 Comments   
Comment by Federico Grilli [ 05/May/21 ]

Integration tests caught an issue with UI not detecting JCR changes, reopening.

Comment by Roman Kovařík [ 06/May/21 ]

For release notes:

Autorefresh of JCR apps content doesn't reacts on changes not visible in grid (such as versioning nodes) anymore which used to cause grid flickering due to server pushing unnecessary data to browser.

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