If you are using JIRA for both requirements capture and defect management, Enterprise Tester is fully integrated to support the synchronization of both requirements and issues. Enterprise Tester supports full bi-directional synchronization of requirementsRequirements/user stories User Stories with JIRA. Key Features include:
...
Project links can be created and managed either from either External Systems in the Admin area tab 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.
The Add External System Link screen will appear. Complete the name and select the Link Source, Requirements. 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. Now you will need to complete the Field Configuration and set up the synchronization schedule. See the Configure the Requirement Link section below.
...
Resources Tab
| Anchor | ||||
|---|---|---|---|---|
|
From the Resources Tab 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 Resources tab in your tree navigator and click to expand ‘Project Link’‘Project Link’.
- Right click on your project and select ‘Add Add New Project Link’Link, the Add External System Link screen 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 Enterprise Tester 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.
...
Once the project requirement link is set up, you will be displayed the screen below and will need to perform additional configuration.
From the Edit Synchronization Configuration screen, click on the ET Configuration tab. Select the ET requirements package you wish to synchronize with. Here you can also select the filter criteria when synchronizing from ET to JIRA. You can filter on Types, Statuses and Priorities. Once you have completed your configuration, click ‘Save’ Save.
Next, click on the External System Configuration. Select the entity type(s) (requirement, stories etc.) to synchronize with Enterprise Tester.
...
You can also select to synchronize sub-tasks related to the entities that meet your selection criteria. Note that the filter values only apply to the parent requirementRequirement/user storyUser Story. All sub-tasks associate to these entities will also be synchronized when you select this option.
Additionally, you can choose to Allow Unassigned issues Issues (see Allow Unassigned issues to be synchronized with JIRA).
...
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 Refresh Lookups which will refresh the JIRA metadata.
Field Mapping
Next, click on the Mapping tab.
This screen displays two tabs for outlining and configuring the steps undertaken when synchronization is initiated.
...
Next, set your field mappings in the direction of Enterprise Tester to External System — you will notice on the screen below that the Field Mapping is not currently configured. Please note that Enterprise Tester will prompt the administrator when a refresh lookup Refresh Lookups is either in progress or is required. This must be completed before configuring your field values. A refresh lookup will Refresh Lookups will ensure that all the custom fields from your defect tracker and associated field values are up-to-date during field mapping.
...
Click to highlight and select ‘Map Fields’ and Map Fields and click on ‘Configure’ Configure from the toolbar. Please note that Enterprise Tester may need to Refresh Lookups before you can proceed with your field configuration.
From the Configure Fields mapping screen, several configurations are automatically created consisting of Copy Field type mappings and direct Map field type mappings.
The Copy Field type mappings are already configured and the value will be copied from Enterprise Tester to JIRA on Synchronization:
...
The Map field type mappings require the field values to be mapped. You can see under the column “Configured Configured = False” that False that the value for these fields has not yet been mapped:
...
- To complete the field mappings, click on the “Type” Map Type Map field and select ‘Edit’ from Edit from the tool bar.
- Complete mapping Enterprise Tester field values to JIRA field values.
- Click “Save”. Save
- Complete mapping field values for “Priority” Priority.
Notes on Field Type Support for Automap and Map Mapping Types
...
| Field Type | Notes |
|---|---|
Date Picker | |
Date Time Picker | |
Global Rank | |
Group Picker (multiple groups) | This field is not supported natively in ET so you will need to use either the copy or set value mapping types |
Group Picker (single group) | This field is not supported natively in ET so you will need to use either the copy or set value mapping types |
Hidden Job Switch | |
Job Checkbox | |
Labels | |
Text Field (multi-line) | |
Select List (cascading) | ET does not have a cascading field to map this to. The only cascading field selected is copied from the defect tracker the "copy" mapping supports this field. |
Text Field (read only) | |
Text Field (single line) | |
URL Field | |
User Picker (multiple users) | As there may be of many users, this isn't suitable as a target for the "map" mapping type. The copy mapping could be used but the same username must exist in both ET and JIRA. |
User Picker (single user) | As there may be of many users, this isn't suitable as a target for the "map" mapping type. The copy mapping could be used but the same username must exist in both ET and JIRA. |
...
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 lookupsRefresh Lookups before the field will be detected.
...
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 view the Synchronization history from both the synchronization configuration 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 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 , 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.
...