Loading Profile...
Various comments on usability issues
I've been using sifter for a few weeks for a client and I have some addition feedback.
- The navigation is not organized in a way I feel is efficient. After traveling through bugs making notes, making changes, the only way I can find my way back to the milestone is to go back to the dashboard and then click the milestone link.
- When I set view settings for a milestone they don't stick. Next time I visit the milestone they've been reset. I don't want to see closed and resolved tickets in the milestone, and I frequently have to change the status, assignee, etc.
- The overview/activity/issues links disappear when I'm viewing an issues list. Again, I need to return to the dashboard to access those links again.
- Links to other issues do not work when enclosed by characters, like parenthesis. (i45) does not get turned into a link.
I too second the API work, by the way.
I understand that you're a small business without much time to work on this (at least what you said a year ago when I got to be an early tester), but I'm not comfortable recommending that any of my client use this service because a) it's not what I consider complete and b) with work progressing so slowly it just doesn't seem like I can feel confident about it.
Thanks!
- The navigation is not organized in a way I feel is efficient. After traveling through bugs making notes, making changes, the only way I can find my way back to the milestone is to go back to the dashboard and then click the milestone link.
- When I set view settings for a milestone they don't stick. Next time I visit the milestone they've been reset. I don't want to see closed and resolved tickets in the milestone, and I frequently have to change the status, assignee, etc.
- The overview/activity/issues links disappear when I'm viewing an issues list. Again, I need to return to the dashboard to access those links again.
- Links to other issues do not work when enclosed by characters, like parenthesis. (i45) does not get turned into a link.
I too second the API work, by the way.
I understand that you're a small business without much time to work on this (at least what you said a year ago when I got to be an early tester), but I'm not comfortable recommending that any of my client use this service because a) it's not what I consider complete and b) with work progressing so slowly it just doesn't seem like I can feel confident about it.
Thanks!
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Sorry for the slow response, this somehow slipped through the cracks. I completely understand your concerns, and the simple answer is that we're actively working to address all of them. That said, if you're not comfortable using or recommending it, just check back in from time to time.
With regards to "travelling through bugs" and not being able to return, it should automatically be returning you to the page you originated from in the same state that you left it. There's also a "Return" link on the right side of the issue detail page for every issue that adjusts and always returns you to where you originated from.
Regarding the view settings not sticking, they're not designed to at this point. While we want to address this long-term, the best way to handle that is with a simple bookmark in your browser. All of the state information is stored in the address bar, and bookmarks should work seamlessly.
The overview/activity/issues links issue is one that we're already designing an update for. The problem is that Sifter has grown and adapted organically, and with those changes, it's been difficult to create a structure and navigation that ties it all together. This is something that we're working on, and I'm pretty happy with progress we're making behind the scenes.
The issue about turning issue references in parentheses to links is one that we can and should address. However, in the short-term, since it will create the link with spaces, it shouldn't be a big loss to not use parentheses.
The API is going slowly, but it is going. In the last 6 months we've been way too concerned about rushing features out the door, and we're starting to get back to designing and creating at a pace that we're comfortable with. It will take some time.
And yes, we are a small business without any full-time employees at this point. I completely understand and can't say that I blame you for not wanting to recommend it. That said, we're profitable and continuing to reinvest our profits in improving Sifter. Growth has slowed a bit, but we are still growing and completely invested in making Sifter a great product.
Thanks for the feedback, and don't count us out.
I’m confident
The company says
this answers the question
EMPLOYEE
