tmetro
- 16
- 25
- 15
- Open ideas
-
-
3 votes2
-
23 votes2
-
4 votes2
-
9 votes1
-
1 votes1
-
32 votes1
-
4 votes1
-
- Completed ideas
-
-
1 votes1
-
4 votes1
-
41 votes2
-
9 votes1
-
20 votes1
-
1 votes1
-
6 votes4
-
21 votes3
don't require membership
completed
-
- Comments
This is a long standing issue with bug trackers. The initial description is often obsolete after a few dozen comments have been posted. The solution is to use a wiki model, and store a history so malicious or incorrect changes can be reverted. Given that many people vote based on the original description, having the best description is important.
1 make the original suggestion community editable - about 1 month ago
Might make sense...might also allow a vocal minority to dominate the voting. I'd rather see a system where the admin has more discretion in granting votes, so the admin can give back votes for items that are confirmed bugs, or to a user that offers up a patch, etc.
0 Reward activity with more votes. - about 1 month ago
If not 8 then what number? Is there a case to be made that the quantity of votes should be relative to the number of suggestions the project has? Such as allocating enough votes so each user can vote for 25% of the suggestions? Or do votes represent some fixed quantity, like developer time per quarter, in which case quantity of suggestions is irrelevant.
0 More Votes - about 1 month ago
I think merging of suggestions, as described here:
http://uservoice.uservoice.com/pages/general/suggestions/7095
is the better approach.
0 grouping similar ideas and voting on groups - about 1 month ago
The work around you suggest only became possible recently with the resolution of another suggestion/bug where items with zero votes would get immediately deleted. And the warning about not entering a suggestion when you have no votes is also new. (Both of these are things I suggested.) But I support this suggestion as well, as noted in my comments to #454.
2 Ability to create new suggestion with zero (0) votes left - 2 months ago
On another suggestion I switched it to the planned state, and was able to submit an official comment, but pressing the submit button didn't clear the comment box. I hit save several times, then refreshed the page and the comment was shown.
In all cases I'm interacting with the suggestion detail page, not the main suggestion list.
1 save button disabled when adding official response - 3 months ago
Is this button dependent on the state of the suggestion? I had switched the state to started, but I don't see why that should prevent submitting an official comment.
1 save button disabled when adding official response - 3 months ago
Take a look at http://16bugs.com/ as a good candidate for integration. They're also a hosted service with a similar Ruby-on-Rails UI style. Undoubtedly users will want to have integration with popular trackers they're already using, but 16bugs might be a good place to start, with good cross-sell opportunities.
1 integrate with other bug tracking systems - 3 months ago
I was in favor of not distinguishing between the two until I ran into the scenario I described over in suggestion 454. You want to encourage users to enter bugs. So if the user declares the entry to be a bug report, you might lift the requirement that they have available votes. In fact you might even award them an extra vote once the bug is confirmed.
0 differentiate between bugs and features - 4 months ago
(continuing) The current system acts as a disincentive. Just today I had to remove my vote on a suggestion to submit a UserVoice bug. Perhaps there is merit to the idea of distinguishing between bugs and suggestions. Although I don't see any good reason to limit users who are prolific at suggesting, as long as the votes are limited.
2 admin should be able to create suggestions with zero votes - 4 months ago
I'd like to amend this suggestion to say that *any* user should be able to create suggestions with zero votes. Consider a scenario in which you are using UserVoice as a simple bug tracker for a project. Do you really want to limit the number of bugs a user can enter? The user may not care about the issue enough to remove a vote from a feature, but you might care to know about the bug.
2 admin should be able to create suggestions with zero votes - 4 months ago
Sounds reasonable, but do you want people piling on votes to the suggestions that are already at the top of the list without having seen the rest of the list?
0 Be able to vote from within the widget - 5 months ago
Nice, but do you really need the UserVoice infrastructure to facilitate that? It doesn't benefit from voting, ranking, or organizing. The only benefit it provides over sending the developer an email is making the compliment public.
0 Add A "Compliment" Section - Say What's Right About Product - 5 months ago
"eliminate the delete buttons?" OK, then how do you delete? When setting up a new suggest list, it comes seeded with three UserVoice-related suggestions from admin. Before deploying the service I'd like to delete them and load in suggestions specific to the project.
0 Undo Deletes! - 5 months ago
Looks good. Thanks!
4 Make suggestion entry box/process more obvious - 5 months ago