Edgewall Software

Changes between Version 1 and Version 2 of Ticket #548, comment 50


Ignore:
Timestamp:
Mar 1, 2014, 8:22:16 AM (6 years ago)
Author:
Peter Suter

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #548, comment 50

    v1 v2  
    11I think it would be helpful to distinguish between the problems and the possible solutions.
    22
    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:
     3Let'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:
    441. The ''component'' selection dropdown can get very long. Selecting a component from such a long list is painful.
    552. The query UI does not easily support queries for all subcomponents.
     
    21214. Extend the existing first-class ticket field ''Component'' to be fully hierarchical.
    2222  * 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.
     235. Use the [query:component=plugin/git plugin/git] and [query:component=plugin/mercurial plugin/mercurial] approach, and implement the missing functionality based on that.
    2424  * (This may first sound like a hack, but it works well enough for the Wiki system!)
    2525  * 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].)
     
    29293 also seems too limited (only one layer). And 4 seems too complicated by default (forces everyone to use fully general component hierarchies).
    3030
    31 2 and / or 5 seem more promising.
     312 and / or 5 seem more promising and in the spirit of Trac's philosophy (minimal but flexible).