Issue Details (XML | Word | Printable)

Key: JRA-7477
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: =Neal Applebaum
Votes: 0
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

preset filters is including closed issues

Created: 27/Jul/05 12:08 PM   Updated: 30/Jul/06 07:34 PM
Component/s: Filtering & Indexing
Affects Version/s: 3.2.1, 3.2.3
Fix Version/s: 3.3

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: =Neal Applebaum, Carl Jones, Mark Chaimungkalanont [Atlassian], markus and Nick Menere [Atlassian]
Since last comment: 2 years, 34 weeks, 1 day ago
Resolution Date: 28/Jul/05 07:41 PM
Labels:


 Description  « Hide
I thought that in version 3.0.3, the preset filters "Assigned to Me" and "Reported by Me" didn't include Closed issues. But I see that since version 3.2.1 at least, these filters do include Closed issues. Can you clarify whether this has always been the case? Normally people don't want to include closed issues in their to-do list.
In fact I was quite sure this used to only show only Open, Unresolved issues, because I had to create a new filter "My Resolved Issues" to see them, since I rarely had "Open" issues assigned to me. These preset filters are pretty useless if they include Closed issues - especially for testers. Thanks.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
markus added a comment - 27/Jul/05 12:46 PM
Interesting. My expectation of the "Reported By Me" portlet would be that it DOES include closed issues. The use case for this portlet (I my opinion) would be that I want to know the current status of the issues that I created, hence I would want to know if the issues have been closed or if they are still outstanding.

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


=Neal Applebaum added a comment - 27/Jul/05 12:59 PM
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?

Nick Menere [Atlassian] added a comment - 27/Jul/05 11:25 PM
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.
We chose this criteria for these portlets as it will only return those issues that are active and still need work done on them. If you wish to see issues that were closed or resolved, it would be quite trivial to include these in a Saved Filter Portlet.

Cheers,
Nick


Mark Chaimungkalanont [Atlassian] added a comment - 28/Jul/05 04:04 AM
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

  • "Assigned to me" -> Unresolved issues, assigned to current user
  • "Reported by me" -> All issues, reported by current user

If you need to, you can also edit these preset filters in the JSPs:
\includes\panels\filters_firsthalf.jsp
\includes\panels\filters_secondhalf.jsp

On the Dashboard

  • "Assigned to me" portlet -> Unresolved issues, assigned to current user
  • "Quick links" portlet -> "Reported Issues" has been renamed "My Unresolved Reported Issues"

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


=Neal Applebaum added a comment - 28/Jul/05 08:40 AM
For me, that still doesn't get me exactly what I want... (and I have basic workflow).
You say:
In Browse Project
  • "Assigned to me" -> Unresolved issues, assigned to current user
  • "Reported by me" -> All issues, reported by current user

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.
For a developer, they only see Unresolved issues, typically.
For testers, they typically see mostly resolved issues, and maybe a few open ones. So, a filter that shows all NOT CLOSED issues assigned to me fits both.
Anyway, what you've done is definitely an improvement, and maybe it's impossible for the preset filters to work for everybody's use, and that's why you can create your own filters, eh?


Mark Chaimungkalanont [Atlassian] added a comment - 28/Jul/05 07:41 PM
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


Carl Jones added a comment - 05/Apr/06 02:08 PM
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:
New - when bugs are created
Assigned - a resouce is identified to work the issue
InProgress - the resource is working on it
Resolved - the resource indicates that they have addressed the issue
Verified - QA (or someone) has "double checked" that the resolution is correct and works
we use this list before release to insure that everything we expect in the release has been checked
Closed - the issue is then closed.
we do this after the release, to indicate that the fixes are "in the product" and/or "in the field".

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?
thanks,
-carl


Nick Menere [Atlassian] added a comment - 10/Apr/06 01:43 AM
Carl,
Check out - JRA-8375

Cheers,
Nick