We are using Jira2.
My modification is in JiraIssueExtractorSensor2.
Following is the usage information copied from that file.
Cheers,
Cedric
* The accepted ant task attributes are:
* <table border='1' cellspacing='0'>
* <tr>
* <th>Attribute</th>
* <th>Description</th>
* <th>Required</th>
* </tr>
* <tr>
* <td>workspace</td>
* <td>This attribute is used to associated a Jira issue with a
Hackystat project.
* This is typically used when Jira issue does contain custom
workspace field.</td>
* <td>Either workspace or workspaceRoot must be set.</td>
* </tr>
* <tr>
* <td>workspaceRoot</td>
* <td>Workspace root is used when Jira issue contains a custom
issue field named "Workspaces".
* For example, if the following is set "workspaceRoot=C:\cvs\"
and Jira provides this
* value "Workspaces=stackyHack", the resulting workspace that
will be sent to
* Hackystat is "C:\cvs\stackyHack".</td>
* <td>Either workspace or workspaceRoot must be set.</td>
* </tr>
* <tr>
* <td>unassignedIssueOwnerHackystatAccountKey</td>
* <td>Jira issue information are sent to the Hackystat account of
the person who is
* assigned the issue. In case when a Jira issue is assigned to
nobody, the issue
* is sent to this accout. If this account is not set, then
unassigned issues will
* not be sent to Hackystat.</td>
* <td>Optional.</td>
* </tr>
* <tr>
* <td>defaultHackystatAccountKey</td>
* <td>In case there is no mapping from Jira user name to Hackystat
account, and
* unassignedIssueOwnerHackystatAccountKey is not set for
unassigned issues,
* the default Hackystat account is used to send issue data if
it is set.</td>
* <td>Optional.</td>
* </tr>
* <tr>
* <td>verbose</td>
* <td>If set to true, information about each file being process
will be logged.
* If false, only error message will be logged.</td>
* <td>Optional. Default is false.</td>
* </tr>
* </table>
Aaron Kagawa wrote:
(a) Which sensor are we currently using in Hackystat---Jira or Jira2?
Cedric?
(b) What are the primary differences between the Jira and Jira2 sensors?
There are a couple upgrades that I made: See
http://www.mail-archive.com/[email protected]/msg01765.html .
However, since then Cedric has changed some things.
(c) Is there a need at this point to have two different versions of
the Jira sensor?
I don't think so.
(d) If the answer to (c) is "no", then should we go ahead and (a)
delete hackySensor_Jira, then (b) rename hackySensor_Jira2 to
hackySensor_Jira, and (c) change all internal references to "Jira2"
to "Jira"?
Yeah, I think so. But, again check with cedric about that.
At 03:32 PM 2/18/2006, you wrote:
Greetings, all,
I was thinking of writing the docbook for the Jira2 sensor, and then
realized that I wasn't quite sure of what's been going on with this
sensor. So, could someone (or two) please reply with their
insights/opinions on the following:
(a) Which sensor are we currently using in Hackystat---Jira or Jira2?
(b) What are the primary differences between the Jira and Jira2 sensors?
(c) Is there a need at this point to have two different versions of
the Jira sensor?
(d) If the answer to (c) is "no", then should we go ahead and (a)
delete hackySensor_Jira, then (b) rename hackySensor_Jira2 to
hackySensor_Jira, and (c) change all internal references to "Jira2"
to "Jira"?
Thanks for your help,
Philip
