Change status easily
Resolving a ticket is: 1.click the ticket 2.click the select box 3 choose "resolved" from list 4.click update ticket
that's 4 clicks
Suggestion: 1.click the ticket 2.instead of using a dropdown list, put 4 links: open, resolve, invalidate, hold and when I click on the link, simply save the new status. The current status would be represented bold and without link etc.
(yeah, I'm lazy :))
And also in the ticket list, an option of changing the status without entering the ticket details page would be very practical in some cases. That's bec. I've so many tickets that are so obvious to understand from the title. Actually we're using a simple todolist with a checkbox, no details, no milestones, no assignments (we assign the tickets by writing the assigned person in paranthesis). Of course doesn't meets our needs but in time we discovered that this way is much more practical than clicking 10 times just to change smt. about ticket in "trac" or bugzilla. And that's why I'm here, trying lighthouse :)
I'm not sure about the latter suggestion bec. it may also make the "ticket listing" page more complicated..
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 Rick on 01 May, 2007 03:16 PM
I've thought about your second idea actually: turning the ticket list into more of a todo list that you can churn through. Anyways, I'll let Justin figure that "User Interface Stuff" :)
The problem with one-click status (or even assigned users) is that it would have to create a new ticket version. Having the dropdowns as well as one-click links could get cluttered. But, if you remove the current dropdowns, you'll get more empty ticket updates. Perhaps I need some logic in the backend to merge sequential updates from the same user though.
Anyways, keep bringing these ideas up. We're already looking at ways to make more advanced/custom ticket processing more efficient and powerful for folks. Also, check out the API, perhaps you can wire something up with it.
2 Posted by Justin Palmer on 02 May, 2007 09:26 AM
I'd like to have the ability in the listing to change the state too. I'll look into this, but as rick said this would create a new ticket version (e.g. comment). I think thats fine, because it would do it anyway in it's current state.
Thanks for the suggestions.
3 Posted by Rick on 02 May, 2007 04:09 PM
I like the idea of collapsing sequential ticket versions by the same author, assuming one or both have an empty body. Well, if you can work something swanky in the UI, I'm all for it.
4 Posted by ben_abuyah on 08 Sep, 2007 11:15 PM
I'd just like to second this point. For me, being able to instantly resolve tickets from the list view would be the single most useful feature. Some tickets need comment logs, attachments, and long descriptions, but some just need to be serially murdered.