Setting up the Jira/Eyes integration

Eyes allows you to annotate any step in the test with one or more issues, as described in the article Add issue and remark regions to the step images. Eyes also allows you to associate such an issue with a Jira issue. You can either create the Jira issue from within Eyes or you can link an existing Jira issue to an Eyes issue. Linking Eyes and Jira issues is described in the article Using the Eyes/Jira integration.

This article describes how to enable and configure the integration of Jira with Eyes. This must be done by a user with Team admin rights. Once the required setup is performed, you will see the option to create and link to a Jira issue in the Test editor or Step editor Create issue dialog.

To set up Jira integration with Eyes, you need to provide three pieces of information:

  • The URL of the Jira Server
  • The ID of your Jira project
  • The ID of the Jira issue type you want Eyes to report

If you do not have these values, then you need to obtain them from the Atlassian site. You might find this link in the Atlassian site helpful: How to get project id from the Jira User Interface.

Setup steps

To set up Jira integration with Eyes, take the following steps:

  1. Load the Admin page using the page selector. Select the Teams panel and click the row for the team you want to configure. On the team configuration page, click on the Integrations tab and then click on the Jira integration icon.
  2. Enter the Jira server URL, the pid (project ID), and the issue type id into the appropriate fields.
  3. Optionally, you can request that Eyes includes other Jira information when creating the Jira issue. Click in the Field name box and select the Jira attribute you want to add, then in the Field value box enter the value you want to associate with that attribute.
  4. A new Field name attribute appears, and you can add additional attributes by repeating the step above.
  5. You can also add pid and issue type information on a per application Every Eyes test is associated with an application name and test name. These uniquely identify the test. The baseline for the test is based on these names along with the OS name, the Browser name and the viewport size. basis by clicking on Add application specific settings and selecting an application from the displayed list. The Test Manager will open a new set of fields, as described above, and you can enter the project ID, issue type, and other Jira attributes for that application. Repeat this step for each application to which you want to give specific Jira values.