first of all, 10,000 cheers for the "my issues" tab now including issues i've replied to, not just ones i authored or which are assigned to me (#52617)! hurray! ;)
however, i just noticed a disagreement between the "my issues" tab and the "track posts" tab regarding an issue i created that's been updated since i last viewed it (#56072). currently, when i refresh the "track posts" tab within my profile page, it's marked with a nice little red "updated". however, using "my issues", it's not listed at all.
the reason is that the issue in question is marked as "by design". even when i stripped out the states argument to the URL, and use this:
http://drupal.org/project/issues/user?participated=46549
it still seems to have hard-coded logic about what states to include in the query. however, once you use the "status" drop-down box to select "all", the query no longer remembers this is supposed to have "user?participated=46549", and you just see all the issues.
it appears that the only way to query for all of your issues is to manually construct a URL with all the possible int values of status, which is kind of a pain, and will probably trip up a lot of users.
i'd like to propose a few possible changes, but i'm curious what other folks think before i start writing a patch for any of them:
- if a /project/issues URL includes a user argument but no states, it should default to *all* states, not just the standard subset (active, code needs review, etc).
- if we're at the query issues form via a /project/issues/user, it should remember that fact and further modifications of the query based on the select boxes should continue to filter by the user.
- perhaps we should add a new dropdown box for "users" that can either be "All", or "[currently-logged-in-user]". unfortunately that wastes a lot of screen real estate. maybe just a checkbox called "my issues" that lived right above the "advanced search" link?
even trying to use advanced search has the same problem. if you just type in your username to "Participant" and try to select all the states, you still only get the hard-coded default states. :( the definitely seems like a full-blown bug, not just a confusing interface.
i'm a pretty clueful drupal user, and after a bit of playing around, it seems the only way to query all your issues is to manually construct the following URL:
http://drupal.org/project/issues/user?states=1,2,3,4,5,6,7,8,9,10,11,12,13,14
that's a bummer. if i submit an issue and someone marks it as "won't fix", "by design", etc, it shouldn't disappear from my default view of my own issues. that makes sense for project admins querying issues to see what needs to be done, but not for users trying to track their own issues.
if anyone likes/dislikes any of the above solutions, please +/-1 them (refer to them by their number in the above list). i think all of them are probably worth doing, but any would solve my immediate problem. and, it's not an accident i'm creating this as a "bug" since i think the current behavior (silently assuming certain states) is a bug, at least when it comes to the "my issues" tab.
thanks in advance for any feedback, positive or negative. ;)
-derek
Comments
Comment #1
Anonymous (not verified) commentedi'll take this one on once the query filter stuff is out of the way.
Comment #2
Anonymous (not verified) commentedComment #3
dww#2 from my original post is now fixed via http://drupal.org/node/97944
that's the only real bug in this issue... the rest of these are feature requests for the UI.
Comment #4
catchhttp://drupal.org/node/187476 was duplicate, and this is a much better idea. :)
Comment #5
aclight commentedLet's revisit this once #76725: Refactor project issue module to use Views is finished.
Comment #6
dwwNow fixed via views: http://drupal.org/project/issues/user
The URL remembers that it's a per-user view, the view can take an argument to view issues for any user, and any filters you apply are always restricted within the general constraint of the user argument.