Details
-
Bug
-
Resolution: Won't Fix
-
Neutral
-
None
-
6.1.6, 6.2.3
-
None
-
Empty show more show less
-
UI Maintenance 3
-
1
Description
Steps to reproduce
Configure a new content type and an app that having a Date property with a dateField, note that the issue is that "time=true" property of dateField was not taken into account by system as ticket description.
- Sample content type config:
datasource: workspace: test autoCreate: true model: properties: - name: title label: Title type: String required: true i18n: true - name: myDate label: Your date type: Date
- Sample app config:
!content-type:test-app name: test-app label: Test icon: icon-app # Optionally override any of the app configuration supplied by the content type. subApps: browser: workbench: contentViews: - name: tree dropConstraint: $type: jcrDropConstraint primaryNodeType: test $type: treeView columns: &columns - name: jcrName label: jcrName $type: jcrTitleColumn editable: true nodeTypeToIcon: mgnl:contact: icon-people mgnl:content: icon-folder editor: availability: nodes: true properties: true - name: title label: Display name filterComponent: &textFilter $type: textField - name: myDate label: Your date $type: dateField type: java.util.Date time: true
Expected results
Support customer to display "time" and save it properly.
Actual results
See illustration image below on 6.2.3, note that we don't have even "time" property to pickup
Workaround
No.
Development notes
Notes to/from developers
Checklists
Acceptance criteria