Hey Guys,
You may or may not have received a bunch of Jira notifications recently
that indicated a change in the workspace field. If you have, then I'm
just letting you know that I did it. I changed a bunch of workspace
fields to better associate software code with the issue. For example, in
this issue
<
http://hackydev.ics.hawaii.edu:8080/browse/HACK-145>, developers
other than Christoph and Cedric will have a hard time figuring out what
code will be changing. Furthermore, I still believe that associating
issues with software code will provide a lot of interesting
possibilities; for example, calculating the active time needed to resolve
the issue. We are probably far from that goal, but getting the workspace
fields correctly associated with software code is the first step. Oh, I
almost forgot to mention that associating issues with workspaces helps my
PRI ranking a lot!
To validate the association between Issues and Software Code, I've
implemented a new feature in the Issue Project Details analysis (on the
analysis webpage). When running this analysis you will see that a column
called "Associated with Code?". This column specifies if a
Issue is associated with Java code. Currently, the only association
that is implemented is with Java code, because we do not have other
DailyProjectData representations for other file types. I have put in a
request with Mike to generate LOCC lines of code data for text files. In
addition, we should probably have a DailyProjectCFileMetric and
DailyProjectCppFileMetric since we already can collect C/C++ filemetric
data with LOCC. (Mike: this isn't really a high priority. in other words
PRI should be fine with only Java associations).
Currently, only 56 of the 190 issues associated with the hacky2004-all
project is correctly associated with Java code. Hopefully that
number will improve. I will continue to look over Issue data and change
workspace fields if I can figure out what code is associated with an
issue.
* If it is not too much trouble, then can you please create Issues with
the fully qualified workspace. I realize that sometimes the exact
workspace isn't known, so I don't expect we will ever reach a 100%
issue-code association.
* Sometimes I can't figure out the issue-code association and just have
to skip the issue. If would be great if you guys could go through some of
the issues and update the workspaces.
* Just a warning.. for issues that are closed, I have to reopen them,
edit the workspace field, and reclose them. This will result in three
Jira notification emails. In addition, this could throw off calculations
of the length time from open to closed. But, I currently don't know that
information is useful or not.
* By the way.. you can associate an issue with more than one workspace.
For example
<
http://hackydev.ics.hawaii.edu:8080/browse/HACK-175>. This issue
has a workspace field =
"hackyIssue\src\org\hackystat\stdext\issue\sdt\,
hackyAnt\src\org\hackystat\stdext\sensor\ant\jira\". Use a comma to
separate workspaces.
thanks, aaron
ps. I also made an improvement to the Jira sensor, described in this
issue
<
http://hackydev.ics.hawaii.edu:8080/browse/HACK-246>. This
improvement sends issues like
<
http://hackydev.ics.hawaii.edu:8080/browse/HACK-2> to a default
user. HACK-2 is assigned to Dan Port, who is not part of the
hacky2004-all project and is not in the usermap.xml file on hackydev.
Therefore, HACK-2 has never been collected by Hackystat. With the
addition of the default user in the Jira sensor, HACK-2 will now be sent
to the default user, which will probably be hackystat-l. Note: I have not
yet upgraded the sensor.jira.jar and build.utils.xml to fully finish this
new feature. I will do so soon.
