(any) as child card type in trees#521

Subscribe to (any) as child card type in trees 3 post(s), 3 voice(s)

 
Avatar Koen De Hondt 56 post(s) #1286

As far as I can tell from the documentation and the experiments I did, Mingle 2.0 supports one 1 card type when defining a tree structure. That does not support my use case.

I like to have a tree like Release > Sprint > (Story, Task, Bug, Investigation) or Release > Sprint > (any), so that I can create sprint cards with child cards of type Story, Task, Bug, or Investigation. In the current version, I can only specify Release > Sprint > Story, but then I cannot add cards of other types to the sprint card, because the filter in the “Add cards to tree” panel does not allow me to select other card types than Release, Sprint and Story.
Is this missing functionality or don’t I understand how to use trees?

Regards,
Koen

 
Avatar Marnen Laibo... 23 post(s) #1363

I think this is similar to my feature request at http://studios.thoughtworks.com/discussion/forums/6/topics/497 . Wanna join that thread?

 
Avatar Suzie Prince Administrator 137 post(s) #1365

Koen

Although you can only configure one card type at each level of a tree, any card can actually belong to any one of its parent card types. So in your example if your tree is called ‘Product’ and contains card types of ‘Release’>‘Sprint’>‘Story’>‘Task’>‘Bug’>‘Investigation’ any ‘Investigation’ could actually fall under any ‘Sprint’, ‘Story’, ‘Task’, ‘Bug’ or under the root node of the ‘Product’ tree itself. The only restriction to the configuration is that a card type configured to be ‘higher’ in the tree structure can not fall under a card type configured as ‘lower’. In this example a ‘Release’ can not belong to a ‘Sprint’ or ‘Story’ etc…

As Marnen said this topic is being discussed at http://studios.thoughtworks.com/discussion/forums/6/topics/497. For more information please take a look at Adam’s initial reply to Marnen as I believe this also answers your question.

I hope that helps.