[MGNLUI-5518] Rename node action is not working when the item has a property 'name' Created: 21/Nov/19  Updated: 30/Sep/21  Resolved: 30/Sep/21

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 6.1.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: maintenance, y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* 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:
Epic Link: Support

 Description   

When there is property 'name' in a node and the node is renamed, the value of the name property is the one taken when renaming instead of the one filled in the dialog.

  1. Create a content app with a property 'name' or add a new propety 'name' to contacts (for example)
  2. Create a new item
  3. Rename the node

The new name is the one in the 'name' property (no the one that was written in the rename dialog).



 Comments   
Comment by Marty Glaubitz [ 18/Dec/19 ]

Affected by this as well, how did this bug slip into the release?!

Also. this bug should get the priority critical

Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

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