| 2006-04-11 13:42:29 |
Euan MacGregor |
bug |
|
|
added bug |
| 2006-04-20 07:21:58 |
Matthew Paul Thomas |
description |
Given that "patch" is a checkbox (and the default is off), it doesn't make sense (to me) to indicate that one must "fill in" that field. |
Given that "patch" is a checkbox (and the default is off), it is misleading for it to be labelled "(Required)".
Since almost all fields in Launchpad forms are required, this can perhaps be fixed by removing "(Required)" from required fields, and instead having "(optional)" next to optional fields. |
|
| 2006-04-24 14:04:34 |
Stuart Bishop |
launchpad: status |
Unconfirmed |
Confirmed |
|
| 2006-04-24 14:04:34 |
Stuart Bishop |
launchpad: statusexplanation |
|
We should update our templates so the required flag is not displayed for radio groups or checkboxes, as the reporter is quite correct that it does not make sense. Better to do this for all forms in one hit.
Internally, the form schemas should remain unchanged as this is purely an artifact of the web UI - submitting information via other mechanisms like XML-RPC we still need to define boolean fields as "must be set explicity and we can't accept no-value". |
|
| 2006-04-24 14:05:11 |
Stuart Bishop |
malone: status |
Unconfirmed |
Rejected |
|
| 2006-04-24 14:05:11 |
Stuart Bishop |
malone: statusexplanation |
|
This is a launchpad wide issue and not Malone specific. |
|
| 2006-04-24 14:08:25 |
Stuart Bishop |
description |
Given that "patch" is a checkbox (and the default is off), it is misleading for it to be labelled "(Required)".
Since almost all fields in Launchpad forms are required, this can perhaps be fixed by removing "(Required)" from required fields, and instead having "(optional)" next to optional fields. |
Flagging checkboxes and radio groups with a 'required' label causes user confusion. Our web templates should not display the label for these controls. |
|
| 2006-04-24 14:08:25 |
Stuart Bishop |
title |
Attachments: Why is the "patch" field "required"? |
Checkboxes should not be flagged as 'required' |
|
| 2006-04-24 15:17:18 |
Björn Tillenius |
description |
Flagging checkboxes and radio groups with a 'required' label causes user confusion. Our web templates should not display the label for these controls. |
Flagging checkboxes and radio groups with a 'required' label causes user confusion. Our web templates should not display the label for these controls.
This will be fixed when https://wiki.launchpad.canonical.com/FormLayout gets implemented. |
|
| 2006-04-24 15:17:28 |
Björn Tillenius |
launchpad: assignee |
|
bjornt |
|
| 2006-04-24 15:17:28 |
Björn Tillenius |
launchpad: statusexplanation |
We should update our templates so the required flag is not displayed for radio groups or checkboxes, as the reporter is quite correct that it does not make sense. Better to do this for all forms in one hit.
Internally, the form schemas should remain unchanged as this is purely an artifact of the web UI - submitting information via other mechanisms like XML-RPC we still need to define boolean fields as "must be set explicity and we can't accept no-value". |
|
|
| 2007-05-15 22:42:05 |
Matthew Paul Thomas |
description |
Flagging checkboxes and radio groups with a 'required' label causes user confusion. Our web templates should not display the label for these controls.
This will be fixed when https://wiki.launchpad.canonical.com/FormLayout gets implemented. |
Flagging checkboxes and radiobutton groups with a 'Required' label (e.g. "Participation essential (Required)" when subscribing to a blueprint) causes user confusion. Our web templates should not display the label for these controls. |
|
| 2008-01-23 19:02:58 |
Björn Tillenius |
launchpad: status |
Confirmed |
Fix Released |
|
