I've always thought of myself as a stack person - if there's an issue that can be fixed now, get it done. Having something languish in a queue means that by th

I've always thought of myself as a stack person - if there's an issue that can be fixed now, get it done. Having something languish in a queue means that by the time you get round to looking at it you may not have all the information you require available / it'll take a lot of time to refamiliarise yourself (most of the time you'll have had to do at least some investigation when the issue first came in in order to determine the impact / priority of the task anyway; if queued all that work needs to be repeated months later). Also, if there's something in a queue which has been there for a year it's probably not that important. If the same thing keeps recurring and you're a stack person, that thing will automatically be jumping to the top of the stack each time - so you can resolve it, then remove any duplicates further down the stack as you hit them. Queues are generally better for project work, Stacks are generally better for support. Regarding the time taken to prioritise and log work, XKCD's nailed it again: http://xkcd.com/1445/ http://xkcd.com/1445/