Excel POP Parser Handler

An Handler that parses an xls mail attachment, producing issues

Description/Features

This handler uses POI to parse an xls file. The file is interpreted using a template, that with an xml-like sintax, binds the xls fields to issue fields.

Install

1. Edit the file com\pronetics\jira\services\messagehandlers\messages.properties in the jar pronetics-excel-pop-service-1.1.jar. Here you must set some parameters.
   mime.type application/vnd.ms-excel
   templates.dir The directory where your templates resides
   issue.type.error If something goes wrong, the handler registers an error into jira. Specify here the issueTypeId that you want to map the error with.
   project.id.error The project id for the error issue.
   default.user The issues will be reported by this user

1. Copy the jar and the poi lib file in the WEB-INF/lib directory
2. Stop jira
3. edit the file WEB-INF\classes\services\com\atlassian\jira\service\services\pop\popservice.xml adding the following lines:

   <value>
      <key>com.pronetics.jira.services.messagehandlers.CreateIssueFromXlsHandler</key>
      <value>Create Issue From Excel Handler</value>
   </value>
   

   under the values of the property handler.

4. Start Jira
5. Create a new service with class com.atlassian.jira.service.services.pop.PopService, using this new handler.
   In the handler-params field, you must specify some configuration parameters. In the next version, all those parameters will be assigned in the <issue> template tag.

• defaultSummary: The summary. You can put template tags here.
• defaultPriorityId: the priority id
• defaultStatusId: the status id

Manual

The received file is checked against a template directory. If a file with the same name exists, the file is parsed. The template itself is an xls file. If you look at the example, you find all the sintax you need for figuring out your use case.

Template Syntax

• <issue project="projectName" type="issueTypeName"></issue>
  Each row find from this block, will be considered to contain an issue. The issue will be recorded in project projectName and will be of type issueTypeName.
• <issue-custom-field name="customFieldName"/>
  This column will be bind to an issue custom field named customFieldName
• <issue-field name="issueFieldName"/>
  This column will be bind to an issue field named issueFieldName