10

We are managing a few independent products (not even many), but between the products, maintenance of old versions and past milestones, there are quite a lot in filters so that I'm hesitant to assign actual milestones, not just releases.

I want to suggest "child milestones", with the follwing functionality:

Milestone 2.4 may have the child milestones 2.4-I and 2.4-II etc.

Showing cases for milestone 2.4 will show all cases assigned to 2.4 or any of its child milestones. Showing cases for 2.4-I will of course only show cases for this milestone.

Selection of milestones in filters etc. uses a tree rather than a list, similar to the "priority" selection dropdown. However, For a collapsed milestone

  [+] 2.4

clickign the [+] will expand, whereas clicking 2.4 selects that milestone.

Recursion (i.e. child milestones for child milestones) doesn't seem necessary to me.

Alternatively, allow partial matches of the milestone, so that 2.4* will match all three milestones. That doesn't help with the size of the list, though.

Workarounds: One could use tags for the sub milestones a sadditional filter element.

Fog Creek Case FC1896146

flag
did you see my comment on my answer below? Is this workaround working out for you? – adambox♦ Jun 7 2010 at 19:31

2 Answers

1

Interesting idea! I have opened a case to consider this feature for a future release. Please up-vote this question to show your support for adding this feature.

Some more alternatives:

  • Searching for fields will find matches for substrings. milestone:"Widget 2.4" matches:
    • Widget 2.4
    • Widget 2.4 beta
    • Widget 2.4.5
  • Sub-milestones could be grouped under parent cases, one for each sub-milestone, with all cases in the same main milestone
link|flag
maybe with a glob: milestone:"Widget 2.4*"? Doesn't help with the length of the list, but they'd at least be grouped correctly, and it's probably much less effort. – peterchen May 18 2010 at 7:58
this should work in search now if you name all your milestones starting with "Widget 2.4". Can you let us know if it doesn't? – adambox♦ May 19 2010 at 14:25
1 
 Sub-milestones would have the added benefit that they could integrate better with reports – David Mitchell Aug 31 2010 at 12:17
@David Mitchell I agree. It would fill a gap that I'm sure many agile teams feel in the current system and would add an additional powerful layer of granularity – cdeszaq Aug 31 2010 at 13:10
would graphical management of milestones and their dependencies, coupled with the search strings above meet your needs? If you can better visualize where your milestones are and manage the order, I think you might not need a hierarchy (which add complexity). – adambox♦ Aug 31 2010 at 14:12
show 1 more comment
-1

I would like to see this as well.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.