JIRA Configuration

JIRA Account

Create a new user account in your JIRA site that will be used by the ExtraView integration daemon to communicate with the JIRA system. Configure this new user with appropriate permissions to access the records and fields that will be replicated by the integration. For example, add the new user to the jira-developers group. Keep a record of the username and password of this new account for the Integration Configuration step.

Integration Fields

The integration daemon requires the use of one custom field for normal operation. Create a new field of Text Field type and configure it with the appropriate Issue Types, Context, and Screens for your JIRA system. This field will be automatically populated by the integration daemon with the ExtraView record identifier (ID) of the ExtraView record mapped to the JIRA record.

For example, the following steps create this required field:

  1. Login to your JIRA system with an administrator-level account
  2. Go to Administration, then Custom Fields
  3. Click Add Custom Field button
  4. Select Text Field as the field type, then click Next button
  5. Type a value in the Field Name (e.g., EV_ID), optionally provide a Description value, use default values for the other settings (i.e., Search Template = "Free Text Searcher", Issue Types = "Any issue type", Global context), and click Finish button
  6. Lastly, on the Screens page select all the screens listed and click Update button

Additional JIRA fields that will be used in the integration should be created and/or configured with the appropriate settings for JIRA such that the user account created above has access to view and update the fields on records.

Attachments

If the attachment field is hidden in the Field Configuration within Jira, attachments cannot be passed between ExtraView and Jira. For further information, see the Jira support website about attachments not showing in API calls:

http://confluence.atlassian.com/display/JIRAKB/Fetching+an+Issue+Via+API+Does+Not+Return+All+fields