Ticket #7015 (new enhancement)
Opened 4 years ago
Last modified 19 months ago
Provide interface to fill custom select-boxes
| Reported by: | Markus.Staab | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | unscheduled |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | ticket, component, custom, interface |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
would be nice to have a interface which can provide data for the selectboxes you can find in the properties fieldset of a ticket.
we have the problem that our software has a lot of plugins which are all described in the trac-wiki and the ticket system is used for managing the bugs etc.
The component select-box is very often not uptodate because someone added a new plugin and this plugin wasn't added to the component list yet.. so the problem is, that nobody can report bugs/feature request which are related to the new plugin..
Attachments
Change History
comment:1 Changed 4 years ago by cboos
- Milestone 0.10.5 deleted
comment:2 Changed 3 years ago by rblank
- Milestone set to 2.0
Components as first-class resources is not on the radar yet.
comment:3 Changed 22 months ago by cboos
- Milestone changed from 2.0 to unscheduled
Milestone 2.0 deleted
comment:4 Changed 19 months ago by cboos
- Milestone changed from triaging to unscheduled



The ideal solution for your situation would be to have components as 1st class resources. Therefore each time you would create and document a new component, it will become available in the drop-down (see #5211).
One interim solution is to give more people the possibility to update the list of components (TICKET_ADMIN + WebAdmin plugin, as you're using 0.10).
The alternative of providing an input text field to all users is a bit risky, as you'll likely end up with duplicate or invalid components.