Loading Profile...
Tickets should be in a queue, the most important first.
Rather than the having discreet priorities critical, high, low etc it would be a lot more useful if tickets were ordered in a queue that way I can pick off the most important task and work on it.
I’m frustrated
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
The best point from the company
-
Because we have a dozen other features that we receive requests for constantly, and we don't make plans for features unless we hear the request from a large number if customers. We're just very cautious about adding new features.
The company thinks
this is one of the best points
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Thanks for the suggestion. We don't have any plans for that right now, but we'll keep it in mind for future enhancements.
I’m thankful for the suggestion
-
Inappropriate?why not? -
Inappropriate?Because we have a dozen other features that we receive requests for constantly, and we don't make plans for features unless we hear the request from a large number if customers. We're just very cautious about adding new features.
The company thinks
this is one of the best points
-
Inappropriate?um ok then how do evangelize my idea?
-
Inappropriate?You already have evangelized it by bringing it up here on Get Satisfaction. If people see it on here and agree, then they'll click the "Me too." button.
However, please don't expect that votes are all that matters when we consider features. Sifter is focused on simplicity, and adding a second layer of prioritization isn't really something that fits in with that. Adding additional attributes to issues, especially when they're moderately redundant, just isn't something that we're likely to do anytime soon.
We do appreciate the feedback, and we keep every request in mind as we make plans for enhancements, but there are hidden costs to every feature, and this is an example of one where we feel those hidden costs are significant. -
Inappropriate?yes and if the focus is on simplicity, how about removing the discreet categories and replacing them for the ability to sort all tickets by priority?
what do you think? this is how someone would normally approach a set of tasks: they can only do one at a time and pick the most urgent one first -
Inappropriate?It's something that we might consider in the future, but it's not something that we currently have any plans for.
-
Inappropriate?I just want to second this request. The priority levels are broad, leaving me with a bunch of high priority tasks without being able to tell which one should be done next.
I'd like have the option to pick off tasks from the top of the list knowing the one up top is the next most important thing that needs to be done.
Something like a drag and drop interface of tasks would make it easy for myself or superiors to quickly rearrange priority as needed.
1 Comment Add a comment
This is one of the best points
-
Thanks for the feedback. We'll keep it in mind for future updates. In the meantime, if you have too many items in the high priority category, I'd suggest making sure to take advantage of the other priorities.
Often times when we hear requests like this, the teams are barely even using anything except critical and high. The reality is that not every issue should be critical or high priority. If some are higher than others, the easiest way to handle that is to take full advantage of the different priorities.
EMPLOYEE
