[MAGNOLIA-8241] Status color is not changed after modifying submodel data for mgnl:content nodes Created: 02/Dec/21  Updated: 09/May/23

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.13
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Jonathan Ayala Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MAGNOLIA-8125 Status color is not changed after mod... Closed
causality
relation
is related to MAGNOLIA-8125 Status color is not changed after mod... Closed
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
Epic Link: Nucleus Quality Maintenance
Story Points: 13
Team: Nucleus

 Description   

Steps to reproduce

  1.  Make use of the attached content app.
  2. Create a new item (STATUS IS RED)
  3. Publish the item (Status is GREEN)
  4. Edit the item by modifying the multivalue field

Expected results

After the modification, status is shown as yellow

Actual results

Status is still green

Development Notes

This ticket is closely related to the fix for MAGNOLIA-8125, which works ok for nodes of type mgnl:contentNode. It seems that the added conditions are not working correctly when the type of the parent node is mgnl:content


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