[MGNLUI-8393] mgnl:createdBy field won't be filled automatically if it's part of the detail subapp Created: 26/Jun/23  Updated: 18/Oct/23  Resolved: 06/Oct/23

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.36
Fix Version/s: 6.3.0, 6.2.40

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Antonín Juran
Resolution: Fixed Votes: 1
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 0.75d Time Spent: 0.75d
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: Zip Archive test.zip    
Issue Links:
causality
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-8394 Implementation Sub-task Completed Antonín Juran  
MGNLUI-8395 Code review Sub-task Completed Quach Hao Thien  
MGNLUI-8396 Pre-integration QA Sub-task Completed Quach Hao Thien  
MGNLUI-8397 Final QA Sub-task Completed Jaromir Sarf  
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
Date of First Response:
Sprint: Nucleus 46
Story Points: 2
Team: Nucleus
Work Started:
Approved:
Yes

 Description   

Steps to reproduce

  1. Define a detail subapp that shows Magnolia metadata fields like "mgnl:createdBy"
  2. Create a new node using such Detail subapp

Find a LM attached with the required Detail subapp, which defines a testApp for it.

Expected results

Field is filled with the correct information, in this case, the creator username.

Actual results

The field is left empty. However, if the field is removed from the detail subapp and a new node is created, the field will be filled without issues.


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