...
- Configurable import filtering by: Type, Status, Priorities, JQL fragments, Components, Affects Version(s), Fix Version(s);
- Optional sub-task synchronization;
- Configurable Synchronization Schedules — Adhoc (manual), Periodic (set time interval) and Daily;
- Custom field support;
- JIRA ID on the requirement in ET;
- Remote links to the Requirement in ET (and test script when linked) added on the JIRA User Story; and
- JIRA workflow transition support from ET.
Creating your Project Link
Once the JIRA connection has been created (see Configuring Enterprise Tester for JIRA 5.2 and Above), you can begin associating projects in the defect tracker with projects in Enterprise Tester. Project links can be created and managed either from either External Systems in the Admin area or from the Resources tab.
External System Links
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.
...
Once you have completed the screen click on OK. The External Links Details screen will appear. Now you will need to complete the Field Configuration and set up the synchronization schedule. See the Synchronizing JIRA Requirements Configure the Requirement Link section below.
Resources Tab
| Anchor | ||||
|---|---|---|---|---|
|
From the Resources Tab in the navigation pane, click to expand "Project Links". To view all configured links for your project, double click on your project.
- Click on the ‘Resources’ tab in your tree navigator and click to expand ‘Project Link’.
- Right click on your project and select ‘Add New Project Link’, the Add Link screen will appear.
Enter in the Name for the link, and select from the dropdowns:
- Source is the entity type you wish to synchronize. Select Requirements
- The ET Project will be pre-selected
- Destination is the configured external system to use for this link. Select your JIRA external system
- Select the JIRA Project to synchronize with.
Configure the Requirement Link
| Anchor | ||||
|---|---|---|---|---|
|
Once the project requirement link is set up, you will be displayed the screen below and will need to perform additional configuration.
...
Note that by default all entities will be synchronized if you do not apply a filter. If the JIRA field values do not appear in the field drop down list, you may need to initiate a refresh lookups which will refresh the JIRA metadata.
Field Mapping
Next, click on the Mapping tab.
...
- To complete the field mappings, click on the “Type” Map field and select ‘Edit’ from the tool bar.
- Complete mapping Enterprise Tester field values to JIRA field values.
- Click “Save”.
- Complete mapping field values for “Priority”.
Notes on Field Type Support for Automap and Map Mapping Types
The following field types from JIRA are not supported by the automap or map mapping types:
...
Another point to note when configuring your field mapping configuration for "Automap" or "Map" type mappings is that you may need at least one value in your JIRA picklist (configurable set of allowable values) for the field (drop down list, checkbox list etc.) for the field to be detected as a configurable field for these mapping types. After adding your value(s) to JIRA you may need to perform a refresh lookups before the field will be detected.
Scheduling Requirement Synchronization
Now that your configuration and field mappings are complete you are ready to synchronize. 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 Requirement Project Links
Deleting requirement project links will stop the synchronization between Enterprise Tester and your external system. When deleting the link you will have the option to delete the link and remove all external link references or to retain these references. These include the trackback comments and the defect issue link placed in Enterprise Tester. Note that if you chose to delete the references. This will only affect Enterprise Tester. References to Enterprise Tester in your external system cannot be removed, but all references in Enterprise Tester to your external system will be removed.
Limitations
When synchronizing from ET to JIRA, requirement to requirement relationships in ET are synchronized to JIRA.
When synchronizing from JIRA to ET, links between issues in JIRA are not synchronized to relationships in ET
Requirement Synchronization to JIRA does not currently support mapping to/from cascading select fields. When synchronizing from ET to JIRA, if you see an error message similar to this with the error "is an invalid parent option" this suggests you have tried mapping to a cascading select field:
No Format System.ServiceModel.FaultException: com.atlassian.JIRA.rpc.exception.RemoteValidationException: Fields not valid for issue: Errors: {customfield_10130=The option '1' is an invalid parent option} Error Messages: Remove the mapping to allow synchronization to work once again.Auto-map from ET to JIRA is not currently implemented (field values from ET are not added to JIRA automatically as they are int he JIRA to ET direction when using the auto-map feature).