[MGNLFORM-6] Dialogs should have label first, not key. Created: 15/Jan/09 Updated: 27/Nov/13 Resolved: 26/Jan/09 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Boris Kraft | Assignee: | Teresa Miyar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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: |
| Description |
|
Currently the dialogs start with the key. (Field Name?). This is counter-intuitive, since the normal users doesn't care about the key. The dialogs for the form fields should start with the Field Label. The key (Field Name) should be an optional entry that defaults to the label. It should probably be the last entry on the dialog. |
| Comments |
| Comment by Philipp Bracher [ 16/Jan/09 ] |
|
I agree that the label should be that top most element. But I would not move it to the bottom as it is quite relevant as soon you want to use the values (to create the email template for instance). Since the field lable can contain values which wont fit the needs for the field name (spaces, ...) I would not base to much on the name=label approach. |
| Comment by Christoph Meier [ 27/Nov/13 ] |
|
it's fixed and very old. |