tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/423-priority-on-ticketsLighthouse: Discussion 2016-09-06T16:11:29Ztag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-22T04:27:27Z2009-04-22T04:27:27ZPriority on tickets<div><p>I'll document the search options, but I don't know how permanent
this change will be. It still doesn't seem that useful for us. But,
we try to keep our iterations short, and our ticket lists small and
sortable.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-22T04:28:00Z2012-07-20T15:36:21ZPriority on tickets<div><p>A Lighthouse ticket was created for this discussion</p></div>Systemtag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-22T11:39:21Z2009-04-22T11:40:34ZPriority on tickets<div><p>Thanks! For the matter of the implementation of priorities: I
don't want to discuss usefullness here (I understand your point of
view with regard to the weighing of priorities). Nevertheless, I
feel you should either implement a 'working solution' or dispose
it. The 'working' part consists of a visual feedback and (less
important) changeset. Now I can set priority, but it's not
visualised in the ticket list and thus rather useless.</p>
<p>The on/off switch enables projectmanagers to chose themselves
the way they want to work. Let them (the market) decide. I noted
that the CSV export includes priorities if these are set,
great!</p>
<p>I hope you can implement these changes.</p></div>johan.sombekketag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T00:50:05Z2009-04-23T00:50:05ZPriority on tickets<div><p>I agree. We had a client that was more comfortable using
priorities with dropdowns (vs the default drag/drop reordering),
which is why we enabled this on a trial basis. We'll probably be
analyzing usage of the participating accounts and emailing the
owners to get a sense of how they're using them. Approximately 7%
of the eligible accounts even have the feature turned on.</p>
<p>At any rate, the priority and sort options <a href=
"http://help.lighthouseapp.com/faqs/getting-started/how-do-i-search-for-tickets">
have been documented</a>. Priority bulk editing <a href=
"http://help.lighthouseapp.com/faqs/ticket-workflow/ticket-keyword-updates">
has also been documented</a> in its FAQ.</p>
<p>It's not deployed yet, but I threw in some initial bubble icons
(see the screenshots).</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T06:40:39Z2009-04-23T06:44:30ZPriority on tickets<div><p>Thanks, looks fine to me!</p>
<p>For the colours; light grey = low, black = neutral and green =
high? Or is green = neutral and black = high? You might consider
picking another colour for 'high' (something orange / yellow / red,
...). Or like you suggested before something like:</p>
<ul>
<li>open circle (low)<br></li>
<li>open circle with dot (neutral)</li>
<li>filled circle (high)</li>
</ul>
<p>These could all be in the same colour range to prevent the
'rainbow' effect.</p></div>johan.sombekketag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T07:44:59Z2009-04-23T07:44:59ZPriority on tickets<div><p>Yea, I actually ripped the icons from Tender. I tried playing
around in Pixelmater and had issues getting something decent. I
mainly wanted to see how it'd look in the layout.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T07:49:17Z2009-04-23T07:49:17ZPriority on tickets<div><p>Rick, I got an idea for the discussion wether or not having
priorities foor tickets. A priority can be defined as a 'attention
mark'. So, in this respect it would be possible to:</p>
<ul>
<li>sort tickets per milestone with drag-and -drop</li>
<li>mark a ticket as requiring attention</li>
</ul>
<p>As a projectmanager I understand your point about weighing
priorities. If you rank them this way, it is unclear whether a
'normal' ticket for milestone A (to be delivered next week) is less
or more important than a 'high' ticket for milestone B, set for
next month. Thus, ranking is done on the basis of milestones, the
sequence (or importance) is done by drag-and drop within a
milestone. Yet, I'd like to know if a ticket requires special
attention. This can be done with the 'attention mark'. And if
someone wants to use this as a 'priority flag', then let them do
so.</p>
<p>The attention marks could be labeled as stated above, maybe you
should not give a meaning to the symbol, but just let the symbol
explain itself:</p>
<ul>
<li>open circle</li>
<li>open circle with dot</li>
<li>filled circle</li>
</ul>
<p>I'm curious how you feel about combining both ways in this
approach.</p></div>johan.sombekketag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T08:05:06Z2009-04-23T08:05:06ZPriority on tickets<div><p>Yes, we tend to do this with a @high tag. Obviously, having the
grey/green bubbles is a much stronger visual indicator of
importance, but it's essentially the same thing. We just happen to
file these <code>@high</code> tickets from a special search bin
into the current sprint's milestone and bump lower priority tickets
to the next one.</p>
<p>I started the 'experimental priority' support as a low-risk way
to try it out. Maybe a sticky flag as you suggested is all that's
needed? Or maybe some people really need that priority dropdown to
make them feel comfortable?</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-04-23T17:08:08Z2009-04-24T06:20:18ZPriority on tickets<div><p>For me a sticky flag would do (a ticket requires my 'special'
attention or not). And of course the possibility to view (filter) a
list of all tickets with this 'attention mark'. But a priority
'flag' is also OK and I'll mark issues this way. With this solution
you can also satisfy your currently 7% using the priority flag (and
that number may grow, because with the current situation people who
really want a priority flag will most probably not choose
Lighthouse as there issue tracking system).</p>
<p>When I think of a one-time solution that fits all, I think I
would opt for:</p>
<ul>
<li>the concept of an attention mark or visual tag, visualised by
symbols (the circles for example). The meaning can then be
user-defined (verbal definition not necessarily supported in
Lighthouse): it can be used as a sticky flag, a priority mark, a
complexity mark, a dependency mark, ...; in any case a mark that
requires visualisation.</li>
<li>a combination of the possibility to rank tickets within a
milestone and at the same time this 'attention mark' for a ticket
(the current setting is one OR the other, but the sticky flag can
be combined with the drag-and-drop ranking within a
milestone).</li>
<li>the possibilty to sort or filter on this mark (this is already
implemented).</li>
<li>you could think of the possibilty to have people define
themselves this visual tag; in project settings you could show a
list of icons; the admin can define a label for each of the icons
(no label = not in use / not shown) and sort these icons. Further
also a label for this visual tag can be set (priority, attention,
urgency, complexity, or whatever....) This label is only shown in
the ticket details, not in the ticket list (lay-out, of course the
icons are shown in the ticket list).</li>
</ul>
<p>With regard to your question: In development projects it is
usual to bump low-prio things to the next milestone / release. With
other projects, like I do myself, it is not possible to simply move
tickets to another milestone. In many European countries (like
Belgium, the Netherlands and the UK) we use Prince 2 project
methodology. In a Prince 2 project one defines
<em>workpackages</em> which deliver certain <em>products</em>. A
product + a due date = a <em>milestone</em>. For each product are
<em>actions</em> (tickets) defined that are needed to deliver the
product. As these products (milestones) differ it is not possible
to simply move actions (tickets) forward to another milestone. This
explains why you are asked for things like priorities and a due
date for a ticket. Well, as soon as you introduce dates for
tickets, things can become pretty complex, but a visual mark...
;-)</p>
<p>Anyway, the decision is up to you! I'm just trying to help and
improve an already wonderful product (because it's so easy to use,
with a clear interface and not cluttered with dozens of functions
one will never use or get used to).</p></div>johan.sombekketag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-01T16:15:24Z2009-06-01T16:15:26ZPriority on tickets<div><p>ticket priority sorting would be a very useful feature, a must
I'd say, it was frustrating subscribing to the service and finding
that you can't sort tickets by priority</p></div>andrestag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-02T01:29:32Z2009-06-02T01:29:32ZPriority on tickets<div><p>Andres: please see the section on sorting at the bottom of our
<a href=
"http://help.lighthouseapp.com/faqs/getting-started/how-do-i-search-for-tickets">
searching FAQ article</a>.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-02T15:24:38Z2009-06-02T15:24:38ZPriority on tickets<div><p>yes, I have seen that, but there's nothing as sorting absolute
priorities, even under different milestones, (like
absolute_position) a little like having a scrum approach built in
as well,</p></div>andrestag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-02T16:03:51Z2009-06-02T16:03:51ZPriority on tickets<div><p>What do you mean by sorting absolute priorities? Do you mean
High/Medium/Low? Just use 1/2/3 for the sorting, it's all the
same.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-02T16:29:42Z2009-06-02T16:29:42ZPriority on tickets<div><p>sorry about the lack of proper explanation on "absolute priority
" what I meant, is a ticket priority independent of the milestone
scope,</p>
<p>like if I do order:ticket-priority I still get them sorted by
milestone, ticket</p>
<p>in the current interface you can arrange ticket priority by
milestone, but you can not give a ticket a priority higher than the
one of the ticket on the following milestone</p>
<p>it implies yet another position attribute, (like
absolute_position) different from the one in the scope of the
milestone,</p>
<p>this also allows prioritizing tickets that don't belong to a
milestone and a "prioritize" button on the ticket view (not just in
the milestone.tickets)</p></div>andrestag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-02T16:33:32Z2009-06-02T16:33:32ZPriority on tickets<div><p>Try using <code>sort:ticket-priority</code> as shown in the
docs. If this doesn't work, let me know what project it is and I'll
take a look.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-15T17:46:22Z2009-06-15T17:46:27ZPriority on tickets<div><p>i'm of the same mindset as andres. right now, it doesn't seem
like you can prioritize one ticket over the other if they are not
in the same milestone or if they are not part of a milestone.</p>
<p>it would be nice to have the "Prioritize" button on the ticket
page as well so that you can change relative rankings outside of
the milestone bucket.</p></div>franklintag:help.lighthouseapp.com,2008-09-20:Comment/1371592009-06-15T18:17:06Z2009-06-15T18:17:06ZPriority on tickets<div><p>You need a paid account to enable the "traditional" global
priority feature in your account settings.</p></div>Rick