Ticket #4374 (new enhancement)
Opened 5 years ago
Last modified 21 months ago
Custom Tickets Select Box Auto-generation
| Reported by: | a.rodger@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | low | Milestone: | next-major-0.1X |
| Component: | ticket system | Version: | 0.10.2 |
| Severity: | normal | Keywords: | tickets custom field |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
It would be nice if instead of specifying all the available options for a select box like:
option1|option2|option3…
in trac.ini, which could run into hundreds, if instead you could specify some kind of query so that this list is automatically generated from the database and keeps up to date. For example, if you had 'is associated with customer' as a select box and the customers are generated from a 'Customers' table in the database. e.g. 'select name from Customer where active=1' so that only customers who are still active (assuming this list changes quite often) are shown in the list.
Apologies for the poor example.
At the moment I have written a script that reads trac.ini and modifies this manually but it is far from ideal as it only runs once a day so the data isnt always up-to-date
Attachments
Change History
comment:1 Changed 5 years ago by cboos
- Milestone set to 2.0
comment:2 Changed 5 years ago by cboos
comment:3 Changed 5 years ago by cboos
- Keywords tickets field added; tickets, removed
comment:4 Changed 2 years ago by cboos
- Milestone changed from 2.0 to unscheduled
Milestone 2.0 deleted
comment:5 Changed 21 months ago by cboos
- Milestone changed from triaging to next-major-0.1X
- Priority changed from normal to low
FieldRefactoring related.



That could be an idea related idea to #2464…
The possible values for a field could depend on those of other fields, for example.
However, the interface will necessarily be much more complex in this case (either use XHR, or without javascript, it would be necessary to update the page after a change, as when adding a filter in custom queries).
For the reason, I'm moving this to 2.0, although the idea is interesting.