Alec Thomas wrote:
Hi,
I'd like to make some changes to the way ticket fields are handled by
Trac, but wanted to see what you guys think before committing any code.
The reason for these changes is so that the workflow API can add hooks
which can control and validate fields in a more flexible manner.
Changes are (from least to most intrusive):
- Add a "disabled" attribute
- Add a "hidden" attribute
- Add a "fullrow" attribute
- Add a "checkbox" field type.
Is a "multiple-select" field possible? I'm not sure if you need another
table to pull this off, but I know that we would like to have a
"Customer" field, and if a ticket applies to one or more customers, they
could be selected in the list box.
ticket_mult_selects
+--------+----------+----------------+
| ticket | field | value |
+--------+----------+----------------+
| 123 | customer | Sun |
| 123 | customer | HP |
+--------+----------+----------------+
and so on.
BA
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
