tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/592-keep-milestone-active-even-if-all-current-tickets-closedLighthouse: Discussion 2011-04-07T05:37:43Ztag:help.lighthouseapp.com,2008-09-20:Comment/18204792010-06-01T04:26:04Z2010-06-01T04:26:04ZKeep milestone active, even if all current tickets closed<div><p>Is it the only milestone you have on the project? So you just
want to keep it active and in front?</p></div>Will Duncantag:help.lighthouseapp.com,2008-09-20:Comment/18204792010-06-02T02:47:10Z2010-06-02T02:47:11ZKeep milestone active, even if all current tickets closed<div><p>No, we have multiple milestones as each project contain a
mixture of support, deployment requests, and scheduled and
unscheduled enhancement tickets for that client.</p></div>James Dellow (at Ripple Effect Group)tag:help.lighthouseapp.com,2008-09-20:Comment/18204792010-06-22T18:11:58Z2010-06-22T18:11:58ZKeep milestone active, even if all current tickets closed<div><p>Running into the same here. I can't assign tickets to a
milestone since LH thinks it's closed. The milestone has no due
date. Is this a bug? If so can it be fixed?</p></div>Martintag:help.lighthouseapp.com,2008-09-20:Comment/18204792010-07-07T04:49:02Z2010-07-07T04:49:02ZKeep milestone active, even if all current tickets closed<div><p>If it has no due date then the milestone, while unscheduled and
showing as closed, can still be used for assigning tickets to. If
it has a date, and all tickets are resolved, and the date is up,
then it can no longer be used for assigning tickets to.</p>
<p>If there is a break in that functionality, then it may be a bug
we're unaware of. I wasn't able to replicate any broken behavior on
our end.</p></div>Will Duncan