...
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 to. 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 Enterprise Tester 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.
...
To create a new project link select "New" from the toolbar, or from the navigator you can right click on your project and select "Add New Project Link" from the menu, or from the navigator you can right click on your project. Complete the details selecting the JIRA connection that you created in the steps outlined in the above section, and your JIRA project to link to. Now click on 'Save'.
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.
...
- Type
- Statuses
- Priorities
- JQL
- Components
- Affected Versions
- Fixed Versions
- Allow Unassigned issues (see Allow Unassigned issues to be synchronized with JIRA)
If no filter criteria is selected all issues logged in the JIRA project will be in scope for synchronization.
...
The Map Fields activity is the only configuration you will need to complete on this screen. Note that it is the only activity that displays false in the Configured column. To configure the field mappings, click to select Map Field and click Config from the toolbar.
The Configure Field Mappings screen will appear and all Enterprise Tester inbuilt fields have pre-set mapping to JIRA inbuilt fields.
Some fields will require mapping or confirmation of the pre-configured mappings. These will be marked as false in the Configured column.
Several configurations are automatically created consisting of Copy Field type mappings and direct Map field type mappings.
...
To complete the field mappings, click on the field row and select Edit from the tool bar.
Complete mapping Enterprise Tester field values to JIRA field values. Where picklist values in Enterprise Tester and JIRA are exact matches, the mappings will be automatically configured.
Click Save Changes.
Complete mapping field values for all fields following steps 1-3.
JIRA to Enterprise Tester Mappings
...
Task | Configurable | Description |
|---|---|---|
Map Fields | Yes | Allows a set of mappings to be configured to transfer information between the JIRA and Enterprise Tester. |
Map Attachments | No | Synchronizes the set of attachments between from JIRA to Enterprise Tester. This will add new attachments that have not been synchronized previously, and remove previously synchronized attachments that have since been removed. |
Synchronize Comments | Yes | Synchronizes all comments added in JIRA to Enterprise Tester. |
Add Trackback Comment | Yes | Adds a comment to the synchronized JIRA incident with a trackback link to the Enterprise Tester incident: Linked to Enterprise Tester incident — e.g. Incident: http://server/EnterpriseTester/#/incident/edit/04e7f9e5-5784-4e94-a863-9ef600f0a935 (Name: ). If a comment already exists with the same value, then the comment is not added. |
Note that all activities are pre-configured including the Map Fields activity. To view the fields that are pre-configured to synchronize, click on Map Field and then click Config from the toolbar.
The Configure Field Mappings screen will appear and a number of JIRA inbuilt fields have pre-set mapping to ET inbuilt fields. These are configured as either Copy Field or Automap field type mappings.
...
The Add Mapping dialog will appear.
Select the type of mapping you wish to create:
...
When configuring an Automap Type field, you will only need to select the JIRA and Enterprise Tester fields that you are mapping. Auto mapping should be used when your Enterprise Tester and JIRA picklist values are exactly the same, it will automatically map the exact matching values and when Synchronizing in the Enterprise Tester to JIRA direction it will also add new values detected from JIRA to your Enterprise Tester picklist.
Copy
When configuring a Copy Field Type field, you will only need to select the JIRA and Enterprise Tester fields that you are mapping. The text or value from the source incident will be copied to the incident in the other system.
Set Field to Value
On synchronization you can set a value for a field to a specified value. You only need to specify the field in Enterprise Tester and the the value you would like to set.
Set Field Value to (if null or empty)
If the field value is null or empty can you set the field to be set to a specified value. For this configuration select the field and the value to set.
Map
When using the map field configuration, you will be required to manually map the field values. This is useful when the values in Enterprise Tester and JIRA are different or if you have more that one value that will map to the same value in the other system.
To complete this configuration, you will need to choose Enterprise Tester and JIRA fields whose values will be synchronized and then you will need to complete mapping any values that do not exist in the system that you are synchronizing to. All values that have exact matches in both systems will automatically be mapped.
Notes on Field Type Support for Automap and Map Mapping Types
...
Click on Add from the toolbar and enter in a name for your task and click OK.
Next, select your JIRA Field and your Enterprise Tester Field and click on Save.
The task is then created, and is displayed in the tasks grid.
From the grid you can see that you are able to configure or disable/enable each task.
...
- Periodic schedule occurring every 1 minute, from the external system which will update all incidents that have been updated since the last synchronization. This is conditional on having been previously synchronized.
- Synchronize on change in Enterprise Tester in the direction of Enterprise Tester to JIRA. A sychronization of all incidents added or updated in Enterprise Tester since last synchronized will be initiated at the time a change occurs to an incident. This synchronization only updates JIRA with the changes made in Enterprise Tester.
The synchronization frequency can also be configured from the Schedules tab. There are 3 options that can be configured:
...
You can use the tool bar to add a new scheduled synchronization, delete an existing configuration, enable or disable an existing schedule, configure an existing schedule or manually initiate a synchronization.
Synchronization History
You can view the synchronization history from both the synchronization configuration screen and the individual synchronized entities. From the configuration screen you can view all synchronization events, select to only view errors, export the synchronization events to a .CSV file or clear the history.
Deleting Project Links
...
| Note |
|---|
Even if you chose to remove references, this will only apply to Enterprise Tester, JIRA issues will still contain trackback links and remote links referring the Enterprise Tester entity they were synchronized with. This information must be removed manually. |
Limitations
When synchronizing from JIRA to Enterprise Tester, links between issues in JIRA are not synchronized to relationships in Enterprise Tester.
Auto-map from Enterprise Tester to JIRA is only supported for the component and version fields, and its use is generally discouraged (adding versions and components to your defect tracker generally makes more sense, so that you can populate additional information such as component lead, due date etc. — which Enterprise Tester does not support).
...