Rawrrrr
People need to understand that prioritisation is not saying everything is top priority. That means they're all the *same* priority and therefore none are a priority! Gah

The creator of the ticket doesn't determine priority, the person(s) fixing it do.

@sylar182 hehe yeah, in Ops world it was easier just to say we're working FIFO so wait your turn.

In delivery side it's more complex, stakeholders make their case to product owner, product owner is the one person who determines priority based on the big picture of all items. Dev team just works off rank 1 onwards.

If anyone questions "why isn't item x (rank 20) done yet?".. well because you said 19 other items are more important :)

@deMark I'm working on creating a ticket system for our office and this was one of my first thoughts. I wanted to make absolutely certain that only the web developers could change the priority on web tickets. When the ticket is created it gets a pending priority. From there it gets assigned a person and a priority by the senior dev.

Just makes it easier for me to prioritize clients who are paying.

@sylar182 a single work queue (edit: per product/website/client) is the way to go, and a single person deciding priorities as well. All dev items, production issues etc all go into the same queue and prioritized against each other. Then it just becomes a stack for your devs where they pop the next item off the top to work on and complete.

I'd recommend reading The Phoenix Project too if you haven't already :)

Also I've just been using off the shelf tools like JIRA..

If everything is important nothing is :)