|
|
|
[
Permlink
| « Hide
]
Benja Kepler added a comment - 02/Sep/07 02:22 AM
The 'Watcher List' feature in JIRA may be of use here.
Guess I'll have to go through and "watch" all my own and my voted issues.
 Sign every comment and always comment when you vote. Then create a filter for Argent Stonecutter's Comments.
Mercia Commenting on everything I vote for doesn't seem like a good solution. Popular items will then be filled with quite a few "I voted for it" comments just so they can keep track in their filter.
I don't understand why "I voted" couldn't be an option to add to the filter settings. This bug/feature list is only going to get larger and better organization tools will help keep it manageable. Removing votes is not a good option. History should be history.
As it is now, watchlist is the way to go. The difference would be you if you would want to be notified for changes on watches and have a larger list of 'open issues I voted on'. Agree, removing votes was at best a bad "last resort" solution.
Amended the proposal to not include that option. "As it is now, watchlist is the way to go."
Not if you have a lot of existing voted issues and no way to convert them in bulk to watched issues. Try the following URL:
Thraxis: what are you getting at? This problem report is about that fact that page doesn't allow you to limit the search to unresolved issues. If there's a way to limit it to unresolved issues that I'm missing, you'll have to explain that.
I mis-read the issue as you didn't provide a link to the page you were talking about (ie. the link I did post)
There is a "Votes View" you can add to your dashboard. When logged into JIRA, click on "HOME" in the upper left. Then click on "Manage Portal", on the right hand side of the page above the filters. Click on "Full Configure" next to the DASHBOARD link in the middle of the screen Click on "Add" Find "Voted Issues" and click on it in the list Goto the bottom of the page and click on "Add" Change the number of items you wish to display, if you want the vote count displayed, and if you wish to display resolved issues or not. Then click on "Save" You can then click on "Home" again, or move it about the page to taste. OK, there were some missing steps, but I sussed them out.
This is a good start, but this only shows a limited number of entries (or makes the dashboard huge), and when I click on the link to see more... all the resolved issues are back in the list. So I'm keeping this one open. I'm going to guess you'll probably need to go to http://jira.atlassian.com
 and file a feature request there for this. 1 - Let's not close this as misfiled. If there is no way to solve it, then let's agree on what we need and how it should be done and then decide who will make a request to Atlassian. If such a request is already in place, whoever finds it, please post here. Alternatively, this issue can help us find other solutions or workarounds.
2 - It is not just votes that have this problem, watches is the same. Slightly less because you can unwatch, but with many watches one starts losing track as well. 3 - The first solution is to have the Watches and Votes list sortable, which they are currently not. But I think that would be just the outcome when the underlying problem is resolved. 4 - The basic problem is in that your vote or your watch is not a searchable (filterable) property. If that would be provided, you could both make your own queries and the Watches and Votes would be sortable and (optionally) configurable, since they would become just a predefined filter. Now why are votes and watches not searchable? It looks like a n-n (well, n-m) relation. But then again, it's just a list. So it could be searchable just as any other field, comments or anything else. Basically one could search for anyone's votes or watches. Hmm, which could be the reason why it is not provided... But I guess the infrastructure should be properly implemented and the option whether to let users have the ability to filter on votes and watches for any text or just their own username would be a server side setting. I'm not sure why the priority was lowered. It isn't getting any better or any closer to being implemented.
Even if Atlassian were to release a new version with this implemented, LL would still have to go through some kind of update process so it isn't entirely out of LL hands. Also, if LL (as the paying customer) were to file the request and/or make a call, I would bet it's more likely to get implemented then if just one of us asks over there, unless we all go register and then vote for the issue... The links to the relevant Atlasian issues are: Duplicate of
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Resolved
Low
"Voted Issues" doesn't seem to be filterable - need new "open issues you've voted on" view, or equivalent.
