[WG: Sakai QA] JIRA Unassigned issues count: 5821

[May, Megan Marie]

Jean-François, 
    What is it your are inferring from the JIRA's being unassigned?   While it's true that unassigned issues aren't being worked on, there are quite a few assigned issues that also aren't being worked on.  Using that as a metric will provide some skewed results. 

Megan 

-----Original Message-----
From: sakai-qa-bounces at collab.sakaiproject.org [mailto:sakai-qa-bounces at collab.sakaiproject.org] On Behalf Of Jean-Francois Leveque
Sent: Friday, October 09, 2009 5:23 AM
To: Sakai QA; Anthony Whyte; Clay Fenlason
Subject: [WG: Sakai QA] JIRA Unassigned issues count: 5821

Hi,

A quick JIRA request with:
- Project: Sakai
- Assignee: Unassigned
shows 5821 issues.

If we select only issue types Bug, Contributed Patch and Tak (Branch, 
Feature Request and Task may not be the one we're looking for), we still 
have 4702 issues.

If we restrict further with Affects Versions 2.6.*, we still have 272 
issues.

Should we have a special assignee for closed issues?

If we restrict again to Status not Closed, we still have 216 issues.

If we last restrict to Resolutions Unresolved and Fixed, we have 212 issues.

I think this is still a lot.

I think this information should be used for our release management of 
both the maintenance releases and the upcoming 2.7 release.

I'm not quite sure how to deal with this but I think something should be 
done.

What do you think?

Cheers,
Jean-Francois
_______________________________________________
sakai-qa mailing list
sakai-qa at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-qa

TO UNSUBSCRIBE: send email to sakai-qa-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"