Changes between Version 1 and Version 2 of Ticket #548, comment 50
- Timestamp:
- Mar 1, 2014, 8:22:16 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #548, comment 50
v1 v2 1 1 I think it would be helpful to distinguish between the problems and the possible solutions. 2 2 3 Let's first describe what is the problem with the current functionality, including using hierarchical `component/subcomponent` names (like e.g. Trac's `plugin/git` and `plugin/mercurial`). I'm not a big user of components myself, but as far as I can tell from the comments above there are two problems:3 Let's first describe what is the problem with the current functionality, including using hierarchical `component/subcomponent` names (like e.g. Trac's [query:component=plugin/git plugin/git] and [query:component=plugin/mercurial plugin/mercurial]). I'm not a big user of components myself, but as far as I can tell from the comments above there are two problems: 4 4 1. The ''component'' selection dropdown can get very long. Selecting a component from such a long list is painful. 5 5 2. The query UI does not easily support queries for all subcomponents. … … 21 21 4. Extend the existing first-class ticket field ''Component'' to be fully hierarchical. 22 22 * E.g. by adding a `parent` to the component DB table. 23 5. Use the `plugin/git` and `plugin/mercurial`approach, and implement the missing functionality based on that.23 5. Use the [query:component=plugin/git plugin/git] and [query:component=plugin/mercurial plugin/mercurial] approach, and implement the missing functionality based on that. 24 24 * (This may first sound like a hack, but it works well enough for the Wiki system!) 25 25 * E.g. use [http://harvesthq.github.io/chosen/ Chosen] (groups and filters) for easier selection in long dropdowns. (Already [comment:26:ticket:918 proposed for multiselection fields].) … … 29 29 3 also seems too limited (only one layer). And 4 seems too complicated by default (forces everyone to use fully general component hierarchies). 30 30 31 2 and / or 5 seem more promising .31 2 and / or 5 seem more promising and in the spirit of Trac's philosophy (minimal but flexible).
