On 08.08.2014 16:51, Christopher Nelson wrote:
But, again, those checkboxes behave like a custom radio button. What
am I missing?
Step back from the query UI for a minute. The type of a custom field
does not describe the query UI. It describes the "modify ticket" UI, the
type of values a ticket can have for that field.
A radio field offers multiple different options. Status is a radio
field! Or imagine a field "Flavor" where a ticket can only have one
flavor. (Up, Down, Strange, Charm, Bottom or Top) So radio buttons are
shown to select that one flavor.
Now back to the query page. What UI should such a radio field show
there? It could be a radio button. That would (only) allow you to query
tickets in one particular option. (E.g. show tickets that have
flavor=charm.)
But as Remy said, multiple checkboxes are just more useful here, as they
also allow querying tickets in a set of options. (E.g. show tickets that
have flavor charm or strange.)
Flavor: ( ) Up ( ) Down ( ) Strange (o) Charm ( ) Bottom ( ) Top
Flavor: [ ] Up [ ] Down [x] Strange [x] Charm [ ] Bottom [ ] Top
It's similar for checkbox fields. On the ticket itself it is a checkbox.
(E.g. Reproduced) On the query page it could be a checkbox, but again as
Remy said the radio buttons allow attaching two labels instead of just one:
Reproduced: [ ] Yes
Reproduced: ( ) Yes (o) No
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
