Assigning a milestone without due date to tickets

Ivo Dancet's Avatar

Ivo Dancet

20 Sep, 2009 12:05 PM

We use a milestone 'urgent' to separate tickets that have to be dealt with immediately from tickets that sit in a release with due date. Off course, we try to keep that milestone empty. The problem is that once the milestone has no open tickets left in it, I cannot select the milestone while creating tickets. (which used to be possible) (and logical as these milestones have no due date)

  1. 1 Posted by Will Duncan on 21 Sep, 2009 11:51 PM

    Will Duncan's Avatar

    Milestones might not be the best way to handle this in Lighthouse for your workflow.

    I suggest you use a tag, like @high, which is independent of the milestone function.

    The do a search, like tagged:"@high" state:open and save it as a ticket bin, creating a counter in the Lighthouse sidebar of that project for urgent tickets.


  2. 2 Posted by Ivo Dancet on 23 Sep, 2009 07:50 PM

    Ivo Dancet's Avatar

    We considered using tags, but our current workflow is like: tickets
    without a milestone need to be assigned to a milestone to know when to
    implement them.

    To know if we have to set a milestone for a ticket will become more
    complicated: instead of milestone:none it will become milestone:none
    not-tagged:@urgent not-tagged:@priority (we have two of those
    milestones) which isn't just as easy on the mind (you have to check
    milestone and tags).

    It's also easy to hide a milestone if it should work like this. One
    just has to set the due date to somewhere in the past (ex: the day the
    last ticket got resolved).

    The reason why we work that way is because not all our tickets are
    about programming. We use lighthouse in all aspects of our company, so
    calling a customer may for example become a ticket at some point.

    I'll change the way we work for now, but maybe you want to consider
    this (old) behaviour again.

  3. 3 Posted by Dave Batton on 14 Oct, 2009 10:26 PM

    Dave Batton's Avatar

    I agree with ivo.dancet. I have a milestone named "Whenever." Works great for my needs, but it becomes unavailable if we complete everything related to that milestone.

    I'd prefer a checkbox for each milestone so I can be the one to decide when it gets hidden.

  4. Nicole closed this discussion on 01 Dec, 2009 07:23 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