Good work, Cedric!
--On Sunday, January 29, 2006 2:24 PM -1000 "(Cedric) Qin ZHANG" <[EMAIL PROTECTED]>
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
To get that number, go into Jira, and produce a report that only filters for project
Hackystat and
fixrelease = 7.3. You should try this out yourself so you know how to use that part of
Jira.
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.
Good!
Therefore, Reducer number (Bypassing DailyProjectIssue project filter) is
correct.
Good!
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"
That's good too. It shows further evidence that we need to make workspaces
case-insensitive.
Did you fix that one?
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.
Excellent! This reveals another thing we need to do: add hackySensor_Jira2 (and
hackyApp_BuildAnalysis) to Hackystat-7. I've just gone to the page and updated the set of
workspaces associated with hackystat-7 (I found a few more that needed to be added in the
process!)
As Aaron said, the sheriff approach is too tedious
I disagree---the sheriff approach works great! The problem is that we don't have good
enough analysis support for the sheriff yet.
Here's one way of looking at it: the fact that the Jira data doesn't quite "match up" is
a form of triangulation---it's a way of doing consistency checking (or triangulation) on
our other representations. This can be extremely useful---for example, it can be a way
of telling us when we need to check our project definitions and add workspaces.
Cedric, since you're the one most involved with this, can you think up a simple
analysis/alert that would help the "sheriff" diagnose and correct "inconsistencies" like
those you've identified?
Cheers,
Philip
