Sub-Milestones or Multiple Milestones Per Ticket

jgraham's Avatar


22 Mar, 2008 05:08 PM

One thing we'd really be interested in seeing is sub-milestones.

What I mean by this, is smaller milestones that are part of a larger one. This would be a great way of 'grouping' tickets.

For example: Milestone1 may depend on Tickets 1, 2 and 3. It also depends on Sub-Milestone A, which depends on Tickets 4, 5 and 6.

This would allow you to see the progress of Sub-Milestone A, as it's own entity, while also making tickets 4, 5, and 6 a part of the total progress of Milestone 1.

Quite often, our milestones may be something like a "Beta 1" release, which includes a lot of smaller pieces we need to work on, Such as a webpage design, a protocol standard, a backend server, a client piece, etc. A system like this would make it considerably easier to monitor the progress of these and determine whether we're slacking off in any particular area... which is quite often the case... we're slackers....

If not sub-milestones, even just having the ability to add tickets to multiple milestones would help. We could then just as easily add a particular ticket to Milestone 1 and Milestone A.

Thanks, in advance.

  1. 1 Posted by Jacek Antonelli on 29 Nov, 2008 07:11 PM

    Jacek Antonelli's Avatar

    I have stumbled upon a way to get fake sub-milestones using ticket bins (or just searching).

    Say you have two milestones, "1.0.0" and "1.0.0 Beta 1". You can search for milestone:"1.0.0 Beta 1" and it will show only tickets for that milestone. But if you search for milestone:"1.0.0", it will show tickets for both 1.0.0 and 1.0.0 Beta 1, since they both match the string "1.0.0".

    You can set up ticket bins for those searches ("Save search"), and it will show you the counts in the sidebar of how many tickets are in that bin. You could combine the milestone search with state:open to make a bin showing how many open tickets there are for 1.0.0 Beta 1, and also make one for 1.0.0 (including Beta 1). Pretty useful for keeping track of progress at a glance.

    This trick would work to an arbitraty "nesting" depth, as long as each sub-milestone name contains the parent milestone's name plus some extra word(s):

    • 1.0.0
    • 1.0.0 Beta
    • 1.0.0 Beta 1
    • 1.0.0 Beta 1a
    • etc.
  2. 2 Posted by Will Duncan on 29 Nov, 2008 10:11 PM

    Will Duncan's Avatar

    that's actually a cool little trick. thanks for sharing.

  3. brandi closed this discussion on 29 Jun, 2012 10:04 PM.

Discussions are closed to public comments.
If you need help with Lighthouse please start a new discussion.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac