Synchronizing Incidents
Creating your Project
...
Links to JIRA
Once the JIRA connection has been created (see JIRA _ Integration), you can begin associating projects in the defect tracker with projects in Enterprise Tester. Project links can be created and managed either from the Resources tab on your tree view navigator or on the External System Links tab.
External System Links Tab
From the Admin tab, Expand Extensions and double click on External Systems. From the External Systems summary grid, double click the External System you wish to create a link for. Then navigate to the Links tab. Click on Add from the tool bar.
The Add External System Link screen will appear. Complete the name and select the Link Source. This is the entity type you wish to synchronize.
Once you have selected the Source additional fields to configure the ET project and the JIRA project will appear.
Once you have completed the screen click on OK. The External Links Details screen will appear. See the Field Configuration section below.
Resources Tab
From the Resources Tab, click to expand "Project Links". To view all configured links for your proejctproject, double click on your project.
...
Once the project link to JIRA has been created, Enterprise Tester will initiate a refresh of all the metadata. This may take a few minutes.
Field Configuration
Once the refresh look up completes the next step is to configure Enterprise Tester inbuilt fields to JIRA fields.
- Click on ‘Configure Inbuilt Fields’.
- Ensure to complete the time offset field this time needs to be the same as the time on your JIRA server. Although this maybe GMT +/- X hour you will need to enter it as GMT -/+ X hours. For instance in New Zealand the time zone is GMT +13 but the setting is GMT -13.
- An optional configuration to pull component and version values from JIRA is available. To enable the auto-mapping of component and version, check the “Auto-map component and versions” check box. When this option is selected you do not need to add values to your pick list for Version and Component fields in Enterprise Tester. Values will automatically be synchronized from JIRA.
...
| Note |
|---|
It is recommended that you align your JIRA and Enterprise Tester picklist values inadvance in advance of this configuration. |
Configuring Custom Fields
Before beginning this configuration, ensure that custom fields have been set up in Enterprise Tester including picklist values, if applicable Click on the 'Configure Custom Fields' button from the External Link Details screen to open the Configure Custom Fields Mapping screen where you can map ET custom fields to JIRA custom fields.
Click on the 'Add' button. For the Internal field, select your Enterprise Tester Custom fields, for your external field, select your JIRA custom field. Click on 'Save'. If you have selected a custom field with multiple values, you will need to map these field values. Click to select your custom field and click on 'Configure'. Map your custom field values and click 'Save'.
The project link will automatically be enabled once the configuration is complete.
Synchronization Monitoring
| Note |
|---|
To view or initiate a full synchronization users require Enterprise Tester Application Administration permissions. |
From the Admin Tab, you can monitor the synchronisation of the defect tracker. Expand your Organisation folder to reveal your Defect Tracker folder. Right click on the Defect Tracker folder and select 'Synchronization Monitor' from the menu. You can monitor synchronization from the Defect Tracker -> Monitor Synchronization link in the Admin Section, from here a simple page is displayed showing the last time synchronization occured - this page also supplies two buttons, allowing immediate triggering of synchronization between the defect tracker(s) and Enterprise Tester (currently by default synchronization of changes in the defect tracker => ET only occurs once per minute).
Caution should be taken when initiating a full synchronization. This will initiate the server to fetch ALL tickets/issues from the defect tracker, this can take a while if there is a large number of tickets. This process is useful when bulk changes may have occured i.e. if a backup of a defect trackers database has occured, requiring resynchronization of all tickets.