[MGNLUI-6073] Name property in content types does not have a label Created: 23/Jul/20  Updated: 19/Nov/20  Resolved: 19/Nov/20

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

Type: Bug Priority: Major
Reporter: Bartosz Staryga Assignee: Unassigned
Resolution: Obsolete Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-07-23 at 15.00.27.png     File event.yaml     File events-app.yaml    
Issue Links:
Relates
relates to CONTTAGS-90 'Tag name' is incorrectly applied to ... Closed
relation
is related to MGNLCT-143 jcrName field added in m6 content-typ... Closed
is related to MGNLUI-6007 Dynamic generated contentType based a... Closed
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: Content Types phase 2

 Description   

When Content app created without `-m5` the name property does not have label (e.g. events-app.jcrName.label)



 Comments   
Comment by Jan Haderka [ 03/Aug/20 ]

regarding a) following content type definition is valid and gives you the label, allowing you to overcome problem with jcr name label caused by CONTTAGS-90

model:
    properties:
    - name: jcrName
      type: text
      required: true
      label: fubar
Comment by Simon Lutz [ 27/Oct/20 ]

Removed the following from the description - solved by MGNLUI-6007.

b) this prop has to have valid jcr node name, which was not the case in old apps

So now we can not just put in the event name e.g.: `Event 2: Christmas Family Photoshoot`
We would have to create a new special field for event title, and still requires users to put valid jcr node name.

Can we bring the old behaviour back?

Comment by Christopher Zimmermann [ 19/Nov/20 ]

I'm thinking this is obsolete. bstaryga can you please check if this is still a problem?

Comment by Bartosz Staryga [ 19/Nov/20 ]

czimmermann Resolved in 6.2.4

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