Enterprise Tester offers a deep integration with JIRA.  Currently, there are two plugins that you can use to integrate with JIRA that are already enabled by default:

  1. JIRA 4-5.1 (Supports JIRA 4.3 - 5.1) Plugin
  2. JIRA (Supports 5.2 and above) Plugin

When setting up your ET to JIRA connection you will need to check which version of JIRA you are integrating with before selecting which plugin to use.  The JIRA 4-5.2 plugin uses the JIRA SOAP service and the JIRA plugin uses the JIRA REST API to connect with integrate with JIRA.

The JIRA Rest plugin offered a richer feature set than the SOAP service and we recommend working with JIRS 5.2 and above so that you can benefit from  the additional features.

You can read more about the two  JIRA Plugins in the following articles: Configuring Enterprise Tester for JIRA 4 - 5.1 and Configuring Enterprise Tester for JIRA 5.2 and above.

Sometimes synchronization is not occurring as you may expect.  Below are some common issues and how to troubleshoot them.  This article assumes that you have configured your connection to JIRA as described in the articles noted above and that you have configured your project links (Synchronizing Incidents with JIRA 4 - 5.1 or Synchronizing Incidents with JIRA 5.2 and above depending on the version of JIRA you are using).

 

Incidents created in ET are not being created in JIRA

 

When synchronizing Incidents with JIRA, the incident created in ET must fulfill the same requirements as when creating an incident directly in JIRA.  This means that when you create the incident in Enterprise Tester all the mandatory fields must be completed including custom fields.

Check the following:

  1. The synchronization history tab of the incident created in ET.  If the issue could not be created in JIRA after synchronizing because it did not meet the requirements for creating an issue in JIRA, a error will be logged here.  You should see an error message similar to the following:

In this message you can see that  the synchronization is failing because the mandatory fields XXX and ZZZ.

in order to resolve this you should:

  • Check if  the fields identified in your error message are custom fields or inbuilt fields
  • Check that you have added a value for the required field in ET ( you may wish to make this field mandatory)

If the field is a custom field, you may need to:

  • Add a custom field and apply it to your incident screen for you project.
  • Add a mapping for your field

 

 

  • No labels