tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/303-adding-tickets-to-milestonesLighthouse: Discussion 2012-07-20T12:23:49Ztag:help.lighthouseapp.com,2008-09-20:Comment/339352009-01-15T00:15:41Z2009-06-20T20:17:17Zadding tickets to milestones<div><p>I would also like this feature.</p></div>Adamtag:help.lighthouseapp.com,2008-09-20:Comment/339352009-01-15T01:20:06Z2009-06-20T20:17:23Zadding tickets to milestones<div><p>We're actually working on a mass edit feature for Lighthouse.
You'll be able to either get a saved ticket bin or write a custom
query, and update several attributes at a time
(tag/milestone/state/assigned user). The backend is done, we're
just waiting on the UI for it.</p>
<p>I'll kick this actual feature request around and see what
everyone thinks.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/339352009-01-15T01:38:18Z2009-06-20T20:17:25Zadding tickets to milestones<div><p>Thanks for quick reply Rick.</p>
<p>My idea for implementing this feature if you're interested: When
viewing the tickets for a milestone
(http://subdomain.lighthouseapp.com/projects/284-name/milestones/1234-name
) there could be a query string parameter added to the "Add
Ticket"<br>
url to auto select the current milestone for the new ticket
(http://subdomain.lighthouseapp.com/projects/284-name/tickets/new?milestone=1234-name
). It's a small change, but streamlines the process.</p></div>Adamtag:help.lighthouseapp.com,2008-09-20:Comment/339352009-01-15T02:10:29Z2009-06-20T20:17:28Zadding tickets to milestones<div><p>Yes, I was thinking of something similar to extra url parameters
or cookies. Using javascript to do the reordering would even keep
the cache valid.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/339352009-03-11T17:08:06Z2012-07-20T15:35:18Zadding tickets to milestones<div><p>A Lighthouse ticket was created for this discussion</p></div>Systemtag:help.lighthouseapp.com,2008-09-20:Comment/339352009-06-08T18:38:50Z2009-06-08T18:38:50Zadding tickets to milestones<div><p>Damn... the recent update to the 'new ticket' form now selects
the top milestone by default, and it's not really what I want
because we add lots of tickets with no milestone. I guess the old
saying is true, be careful what you wish for.</p></div>Johntag:help.lighthouseapp.com,2008-09-20:Comment/339352009-06-09T16:25:37Z2009-06-09T16:25:37Zadding tickets to milestones<div><p>Agree with John with the changes to the new/edit ticket form. So
many tickets are now being created or updated with the incorrect
milestone at our company. Not all tickets fall under a milestone so
people don't think to look there if they don't already have one in
mind.</p></div>Adamtag:help.lighthouseapp.com,2008-09-20:Comment/339352009-06-09T17:59:11Z2009-06-09T17:59:11Zadding tickets to milestones<div><p>There was another thread on this actually. It was some odd
behavior someone added, and I reverted and deployed the fix this
morning.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/339352009-06-09T18:27:58Z2009-06-09T18:27:58Zadding tickets to milestones<div><p>Awesome, thanks for taking care of this so quickly.</p></div>Adamtag:help.lighthouseapp.com,2008-09-20:Comment/339352009-06-17T19:37:57Z2009-06-17T19:37:57Zadding tickets to milestones<div><p>I think the way it works now with the recent changes is good -
you can set a default milestone for a project now if you want that
behaviour. I'll resolve this discussion if nobody objects in the
next couple of days.</p></div>John