[MAGNOLIA-8125] Status color is not changed after modifying submodel data Created: 19/Feb/21  Updated: 04/Aug/22  Resolved: 20/Jul/21

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

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Roman Kovařík
Resolution: Fixed Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: 1d 4h 1m
Original Estimate: Not Specified

Attachments: File tourGuide.yaml     File tourGuides.yaml    
Issue Links:
Cloners
is cloned by MAGNOLIA-8241 Status color is not changed after mod... Open
Relates
causality
is causing MAGNOLIA-8514 Modified date is not updated after ch... Closed
relation
is related to MAGNOLIA-8241 Status color is not changed after mod... Open
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
Date of First Response:
Sprint: Maintenance 64, Maintenance 65, Maintenance 66
Story Points: 13

 Description   

Steps to reproduce

  1.  Make use of the attached sample tourGuide: content-type and content-app 
  2. Create a new item in tourGuides app (STATUS IS RED)
  3. Publish the item (Status is GREEN)
  4. Edit the submodel properties of the item (Contact and address fields) and save changes

Expected results

After the modification, status is shown as yellow

Actual results

Status is still green, which is confusing as it seems as if it was already published when it is not.

Development Notes

If one of the fields of the main model is modified, status is correctly shown in yellow. Modifications are actually saved in JCR as well as the modification dates. It seems that only modifications from the root model are considered



 Comments   
Comment by Federico Grilli [ 21/Jun/21 ]

Postponed to 6.2.11 as this is less straightforward than it looks (see the two PRs and comments there). We'd rather give more thought to it and not rush any workaround or potentially breaking solution.  

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