|
Yeah - I agree with Markus... Reported by Me should also include Closed issues. But adding to the confusion is that there's an inconsistency between "Reported Issues" as a quick link on the dashboard (which only shows unresolved issues), and "Reported by me" preset filter on the browse project page which shows all issues.
But as for Assigned to me on the browse project page.. what is the use case that people would often want to see closed issues assigned to them? Neal,
Can I ask if you are using a custom workflow and screens that allow you to close an issue without setting a resolution? These portlets return those issues with no resolution. So if you modified your workflow such that an issue can be closed and have no resolution, it will be returned. Cheers, Neal & Markus,
Sorry I think our wires got a bit crossed here. We thought Neal was still talking about the "Assign to Me PORTLET" and not the "FILTER". By the looks of things, the FILTER have always included all issues assigned to you regardless of resolution / status. A possible use case for this may be see how much work you've done on a particular project. I agree that this is counter-intuitive and and I've updated the filter to match the "Assign to Me PORTLET" where it will only show unresolved issues. I have left "Reported By Me FILTER" alone and renamed the "Reported By Me QUICKLINK". to be "My Unresolved Reported Issues" to be more precise. So in summary for 3.3: In Browse Project
If you need to, you can also edit these preset filters in the JSPs: On the Dashboard
For customizing these portlets, check out: http://confluence.atlassian.com/display/JIRA/How+to+Create+a+JIRA+Portlet I think this has been a bit confusing for everyone and we all have slightly differing views of the ideal usages of JIRA (which is fine), but hopefully we've clarified / fixed a few things now. Hopefully you'll find something up there that can be an acceptable solution for you! Cheers, Mark C For me, that still doesn't get me exactly what I want... (and I have basic workflow).
You say: In Browse Project
I think the point Markus and I are trying to make is that In Browse Project: "Assigned to me" it should show all NOT CLOSED issues, assigned to current user - Unresolved, AND Resolved. But filtering out the closed issues is still definitely an improvement over the current functionality. For us, developers resolve issues to testers. Testers close them. Neal,
I'll close this issue now since the "Bug" is guess is resolved. I guess the real improvement you're after this as an admin, being able to configure the default filters on the browse project page to comply with whatever usage of JIRA you have. Cheers Mark C I echo what Neal last said. Developers see unresolved bugs. QA sees resolved bugs. QA's job is to test whether the resolution is correct or works. If it does work, they verify (and eventually close). If not, they send back to development. Therefore, QA need to see bugs that have a "resolution value other than UNRESOLVED". I think the main issue is that the resolution value is used by the filters,and not the issue state.
Example: I'd like to see the "Assigned to Me" filter show all NOT-CLOSED issues. Do you know if there is an issue filed for Jira to look at this? |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I believe that the difficulty is this portlet and the Assign to Me portlet is in defining the expected use case. (See http://jira.atlassian.com/browse/JRA-7420
for a similar conversation.)
In addition, I do not think that an end user should be able to modify the portlets to optionally include CLOSED items, or items in another state. why not? from a project management point of view, i would want to be certain that all folks are having the same experience. If, for example, the individual user could modify what sort of issues are included, it might be difficult to ensure that all users have the same functionality. On the other hand, if the sort of configuration parameter could be performed either on a global or project-by-project basis, that might be a agreeable solution.
-markus