Prority of tickets
How can i set the priority of Tickets like high,medium, or low?
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Will Duncan on 02 Jan, 2009 10:37 AM
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.
There are two ways in which you can prioritize your workflow.
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
responsible:me sort:priority milestone:nextwhich 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.Tags: This is a very powerful way to handle ticket organization. If you have a critical issue, tag it something like
@high, letting anyone who knows to look at @high what must be done right away. You can create a universal bin even,tagged:@highso 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 asresponsible:me tagged:@high<br/>Of course you could also have
@medand@lowas tags, and create universal searches for those as well. But in our workflow there is @high and everything else.