Hey Guys,
We've (Burt and I) been hacking on a new DailyProjectIssue class. Currently, we've implemented a functioning DailyProjectIssue class. To demonstrate its capabilities I've posted a sample result of the Daily Project Details analysis; <http://csdl.ics.hawaii.edu/~kagawaa/issue/daily_project_details.htm>. In this page, notice the two new sections; the Issues section in the Project Summary and the "Issues (Total/Open/In Progress/Resolved/Closed) by Top-Level Workspace" in the drill down section.
Here is a little explanation.
The DailyProjectIssues class provides a snap-shot of all the issues in Jira on a given day. Therefore, we can create telemetry analyses that show a range of information. For example, the trend of the number of Major issues over time. Currently, the DailyProjectIssue class only reports on the Status of an Issue (ie. Open, Closed, In Progress, etc), but adding other interesting attributes (type: defect or enhancement, severity: major, minor, etc)of an issue should be easy.
However, what is not possible is finding the number of issues that are assigned to a specific member of a project. Doing this simple task is quite hard. Here's why. Below is a sample Issue Entry:
<entry tstamp="1108437055578" tool="Jira" id="HACK-105" summary="persist the workspace mapping" type="Improvement" priority="Major" status="Closed" creationDate="1099630299000" assignee="kagawaa" reporter="johnson" workspaces="c:/jira/hackyStdExt/src/org/hackystat/stdext/workspace/map/javamap" runtime="1108437054687" data="link=http://hackydev.ics.hawaii.edu:8080/browse/HACK-105"; />
As you can see there are two fields that specify the username of the assignee and reporter associated with the Issue. One could imagine sending this entry to the assignee's Hackystat account using the Sensor UserMap. However, what I can't figure out is how to deal with the reporter attribute if we do this. I believe this is the first Sensor Data Type that could span more than one Hackystat account and it could get a little complicated. Therefore, for now I'm not going to attempt that.
Last of all, there are few Jira Issues with bogus workspaces (there are 38 total issues that cannot be associated with the hacky2004-all project): ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-10 ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-100 ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-101 ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-106 ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-110 ignored issue = link= http://hackydev.ics.hawaii.edu:8080/browse/HACK-113
We'd appreciate any comments and suggestions. For now, I'm going to commit the new DailyProjectIssues class but exclude it from the Daily Project Details analysis.
thanks, aaron
ps. by the way. we've finished implementing a new Ant Based Jira Sensor. You can try it out by running "ant jiraAll". Soon we will be adding that to sensor to the nightly build.
