[HACKYSTAT-DEV-L] JIRA suggestions

[Aaron Kagawa]

Hey Guys,

I've been doing some work with Jira and I noticed a few things about JIRA 
on HackyDev.

1) We are using a pretty old version of JIRA. Jira is at 3.3.1 we are using 
3.1.1.
2) In both 3.1.1 and 3.3.1, we could be using the Version Control Tab which 
links into CVS to provide an association of Commit info with Issue info. 
this could be a very cool way to enhance the Jira sensor to provide more 
useful Issue analyses.  For example, comparing code churn associated with 
bugs versus the code churn associated with improvements.  See 
<http://www.atlassian.com/software/jira/docs/v3.1.1/cvs_integration.html>. 
They also have a subversion plugin.
3) In both 3.1.1 and 3.3.1, we could be using Components. See 
<http://www.atlassian.com/software/jira/docs/v3.1.1/projects.html#components>. 
Basically, this page 
<http://hackydev.ics.hawaii.edu:8080/browse/HACK?report=com.atlassian.jira.plugin.system.project:openissues-panel> 
could show all the issues associated with hackyBuild, hackyKernel, 
hackyStdExt, etc... Right now, we do not have any components defined, so 
this page shows 95 open issues in the "No Component" section.  I would 
suspect that the Jira sensor could again be enhanced to optionally read the 
component field.

thanks, aaron