It seems that we are moving to Jira sensor 2. Let me point out a
potential jira issue - project mapping problem we currently have.
Currently, the mapping is done in the following way:
* When creating an issue, we have a custom field called "Worksapces" we
can fill out like "hackyCore_Build,hackyCore_Doc".
* The jira sensor appends a prefix "C:/jira" when sending data
* Then on the server side, the workspaces become
"C:/jira/hackyCore_build;C:/jira/hackyCore_Doc".
* Then our usual project workspace mechanism kicks in.
The problem with that user can put anything in "Worksapces" field. The
result is not all issues are included when we run Hackystat-7 issue
related analysis. I do find such cases on our public server.
The solution:
1. Use another mapping mechanism, such as through Jira project field.
2. Designate somebody as a police to manually make sure all "Workspaces"
fields are correct.
Cheers,
Cedric
Philip Johnson wrote:
Based on the following, it sounds like we should move toward
replacing hackySensor_Jira by hackySensor_Jira2 for Release 7.3.
This also affects Cedric, since he's working on reduction functions
for Jira issues.
Any thoughts?
Cheers,
Philip
------------ Forwarded Message ------------
Date: Tuesday, January 24, 2006 11:59 PM -1000
From: Aaron Kagawa <[EMAIL PROTECTED]>
To: Philip Johnson <[EMAIL PROTECTED]>, Julie Ann Sakuda
<[EMAIL PROTECTED]>
Cc: aaron Kagawa <[EMAIL PROTECTED]>
Subject: Jira2 features
Hey Philip and Julie,
Here is a list of features that Jira2 sensor provides (as written in
a hackystat-dev-l
email a long time ago
http://www.mail-archive.com/[email protected]/msg01406.html).
I also added this
information to http://hackydev.ics.hawaii.edu:8080/browse/HACK-353 .
I've made a couple of improvements to the Jira sensor.
1) the JiraIssueExtractor can get issue xml files from login
protected Jira projects. It
can also work through SSL. This code is based on the Maven Jira Plugin
(http://maven.apache.org/reference/plugins/jira/).
2) the JiraIssueExtractorSensor has a couple more optional attributes:
- workspaceRoot - use this attribute if your jira server has a custom
workspace field
- workspace - use this attribute if you don't have a custom workspace
field (ikayzo.org
is using this, but i hacked a specialized sensor for them. now we can
just release a
single sensor. i also plan to use this sensor at work)
- unassignedIssueOwner - use this attribute if you want to send
unassigned data to a
hackystat account
- defaultUser - user this attribute if you want to disregard the
issue owner and send all
data to a single hackystat account, useful in situations when jira
users don't have
hackystat accounts or don't know that hackystat exists (ikayzo.org is
using this, but i
hacked a specialized sensor for them. now we can just release a
single sensor. i also
plan to use this sensor at work)
Instead of directly hacking the existing Jira sensor, I made another
sensor call Jira2
that lives in hackyAnt. I suppose Philip can decide whether to
immediately replace the
old jira sensor or to roll out both version. The Jira2 sensor uses
commons-httpclient-2.0.2 and commons-logging.
Pending Issues:
- http://hackydev.ics.hawaii.edu:8080/browse/HACK-510 (write docbook
for the sensor)
- http://hackydev.ics.hawaii.edu:8080/browse/HACK-382 (I think Julie
solved this one
already).
I think hackySensor_Jira2 is a good improvement. It provides
functionality to get at
login protected Jira issues and also merges the Ikayzo specialized
Jira sensor and our
current sensor into one.
thanks, aaron
---------- End Forwarded Message ----------
