tag:help.lighthouseapp.com,2008-09-20:/discussions/problems/1073-assigning-a-milestone-without-due-date-to-ticketsLighthouse: Discussion 2011-04-07T05:36:20Ztag:help.lighthouseapp.com,2008-09-20:Comment/3883112009-09-20T12:05:22Z2009-09-20T12:05:22ZAssigning a milestone without due date to tickets<div><p>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)</p></div>Ivo Dancettag:help.lighthouseapp.com,2008-09-20:Comment/3883112009-09-21T23:51:21Z2009-09-21T23:51:21ZAssigning a milestone without due date to tickets<div><p>Milestones might not be the best way to handle this in
Lighthouse for your workflow.</p>
<p>I suggest you use a tag, like @high, which is independent of the
milestone function.</p>
<p>The do a search, like <code>tagged:"@high" state:open</code> and
save it as a ticket bin, creating a counter in the Lighthouse
sidebar of that project for urgent tickets.</p>
<p><img src=
"http://img.skitch.com/20090921-kingj2kw8hqrphjjpanqemy7ju.png"
alt="img"></p></div>Will Duncantag:help.lighthouseapp.com,2008-09-20:Comment/3883112009-09-23T19:50:24Z2009-09-23T19:50:24ZAssigning a milestone without due date to tickets<div><p>We considered using tags, but our current workflow is like:
tickets<br>
without a milestone need to be assigned to a milestone to know when
to<br>
implement them.</p>
<p>To know if we have to set a milestone for a ticket will become
more<br>
complicated: instead of milestone:none it will become
milestone:none<br>
not-tagged:@urgent not-tagged:@priority (we have two of those<br>
milestones) which isn't just as easy on the mind (you have to
check<br>
milestone and tags).</p>
<p>It's also easy to hide a milestone if it should work like this.
One<br>
just has to set the due date to somewhere in the past (ex: the day
the<br>
last ticket got resolved).</p>
<p>The reason why we work that way is because not all our tickets
are<br>
about programming. We use lighthouse in all aspects of our company,
so<br>
calling a customer may for example become a ticket at some
point.</p>
<p>I'll change the way we work for now, but maybe you want to
consider<br>
this (old) behaviour again.</p></div>Ivo Dancettag:help.lighthouseapp.com,2008-09-20:Comment/3883112009-10-14T22:26:58Z2009-10-14T22:26:59ZAssigning a milestone without due date to tickets<div><p>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.</p>
<p>I'd prefer a checkbox for each milestone so I can be the one to
decide when it gets hidden.</p></div>Dave Batton