tag:help.lighthouseapp.com,2008-09-20:/discussions/questions/123-prority-of-ticketsLighthouse: Discussion 2011-04-07T05:34:47Ztag:help.lighthouseapp.com,2008-09-20:Comment/294522009-01-02T10:37:03Z2009-06-20T20:13:40ZPrority of tickets<div><p>Lighthouse isn't really designed around a ticket priority
workflow. In our mind, tickets are either important or they're not
important, which is the premise of how Lighthouse allows you to
organize things.</p>
<p>There are two ways in which you can prioritize your
workflow.</p>
<p>Milestones: In an application life cycle you will probably
create milestones in Lighthouse, or goals. In Milestone view, you
can drag tickets to set their order in which they should appear.
You can add a ticket bin to your sidebar, such as
<code>responsible:me sort:priority milestone:next</code> which will
give the results of the next upcoming milestone with tickets
assigned to you and in the order you set them. This is more about
the order you want to set your to-do list though.</p>
<p>Tags: This is a very powerful way to handle ticket organization.
If you have a critical issue, tag it something like
<code>@high</code>, letting anyone who knows to look at @high what
must be done right away. You can create a universal bin even,
<code>tagged:@high</code> so all project members can see them on a
universal level. If they need to know what is explicitly assigned
to them, they will need to create their own ticket bin, such as
<code>responsible:me tagged:@high<br/></code></p>
<p>Of course you could also have <code>@med</code> and
<code>@low</code> as tags, and create universal searches for those
as well. But in our workflow there is @high and everything
else.</p></div>Will Duncan