Hi, Philip,
==>The difference is 1 open issue, HACK-495, which is assigned to Lorin,
who is either not a member of Hackystat-7 or does not have a user
mapping or both.
I can send all non-mapped user issue data to Hackystat-l account, but
you still have to include Lorin in Hackystat-7 project definition.
==>I suggest everybody go through his/her own assigned 7.3 issues.
I designed a telemetry scene monitoring this, I will put it on telemetry
wall on Monday. As of now, the number of 7.3 Jira not in hackystat-7
project is:
philip = 0
cedric = 5
hongbing = 0
mike = 2
auten = 0
julie = 1
hackystat-l = 1
I'll check mine myself.
Thanks.
Cedric
(Cedric) Qin ZHANG wrote:
My reducer data is yesterday's. Today's data is:
Jira reports (true number)
total = 42 (actually, I don't know how to get this number in Jira,
it's what you told me).
open = 23
in progress = 5
reopened = 1
Reducer number - Bypassing DailyProjectIssue project filter:
total = 41
open = 22
in progress = 5
reopened = 1
The difference is 1 open issue, HACK-495, which is assigned to Lorin,
who is either not a member of Hackystat-7 or does not have a user
mapping or both.
Therefore, Reducer number (Bypassing DailyProjectIssue project filter)
is correct.
If we use project filter, then
total = 29
open = 16
in progress = 3
reopened = 0
for "reopened"
HACK-485 "hackySensor_CLI" should be "hackySensor_Cli"
for "in progress"
HACK-519 workspace is sclc, not in Hackystat-7, this is ok.
HACK-353 hackySensor_Jira2, Hackystat-7 definition does not include
this one.
for "open"
HACK-512 hackyApp_BuildAnalysis, Hackystat-7 definition does not
include this one.
...
As Aaron said, the sheriff approach is too tedious
...
I suggest everybody go through his/her own assigned 7.3 issues.
Cheers,
Cedric
Philip Johnson wrote:
I just checked Jira, and when I filtered on "Hackystat" and "Fix
For" 7.3, I got a total of 42 issues, of which 41 had an assigned
workspace field.
The "QuickFix" issue does not have a workspace, and there are four or
so issues that have workspace fields that do not relate to
hackystat-7 (i.e. sclc, hackyDevSite, etc.).
Cedric, could you look at this more closely to determine if there is
a bug in the Issue reducer or sensor? As far as I can see, the Jira
issues are all filled out correctly.
Cheers,
Philip
--On Sunday, January 29, 2006 1:17 AM -1000 "(Cedric) Qin ZHANG"
<[EMAIL PROTECTED]> wrote:
Hi,
As our early discussion, we decide to manually make sure that all jira
issues have the correct workspace field.
I added one feature to the issue reducer: it can now bypass
DailyProjectIssue project filtering mechanism and fetch raw issue sdt
directly.
The result:
* We have in total 39 issues tagged for 7.3 release.
* If we use issue workspace field to determine whether it belongs to
Hackystat-7 project or not, then this number is 27 instead of 39.
Though there are some 7.3 issues that does not belong to Hackystat-7
(e.g. I have one related to improving sclc counter), the difference
between 39 and 27 does indicate to me that there are still some issues
with wrong workspace field.
Cheers,
Cedric
