...
The ability to interface with multiple External Systems (Defect Trackersexternal systems (defect trackers, ALMs, EA etc.) is another key feature of the tool. This interface allows incidents and/or requirements (depending on the tool you are integrating with) to be synchronized between Enterprise Tester and the External System. For requirementsexternal system. When synchronizing with JIRA, TFS and Rally, for all supported entities, full bi-directional synchronization is supported regardless of the system the entity (requirement / user story / ncidentincident / defect) was originally created in. For incidents/defectsThe direction and scope of the synchronization is configurable when working with these external systems. When synchronizing with EA, only entities originally created in Enterprise Tester will synchronize with the external system. After the incident is created in the external system, updates made in either Enterprise Tester or the external system will synchronizeEA and imported into ET will be included in the synchronization. Only requirement updates are supported when synchronizing from ET to EA. For more information, please see the help article related to your external system in the list of help topics for configuring project links below.
Enterprise Tester interfaces with the following:
...
Enterprise Tester adds a reference to the external system ticket ID on the entityincident. This This is visible as a hyperlink on the entity or in the Issue ID External Identifiers column of the entity summary screen grid.
Entity
Summary Grid
Add an External System
To add a connection to an External Systemexternal system:
- Open the ‘Admin’ tab the Admin tab of the tree view.
- Click on on Extensions and and double click External External Systems on on the navigator.
.
- From the the External System summary Systems summary screen, you can view all existing connections and view their enabled and configuration status. Click on add from the tool bar Click on Add from the toolbar and add a Name name for your external system connection and select a connection type: Enterprise Architect, JIRA ( 4 - 5.1), JIRA, Rally or TFS
...
- The configuration screen of the external system type you chose will appear:
Enterprise Architect
Connection Type | Select the EA repository type from the drop down list. |
Connection String | The connection string details are dependent on the connection type. See the Enterprise Architect help topic for more information. |
| Disable Import Feature | This feature disables the ability to import from EA. It can be useful if you would like to enable the feature for an import and then disable them after the process is complete to limit other users from initiating the process. When disabled, the Import button is no longer available on the project link screen. |
| Disable Update EA Feature | This feature disables the ability to update EA with the changes made in ET (updates and deletions). As the update feature will update all values in EA regardless of which system holds the latest change, this feature can give you some control over when updates are made. When disabled the Update EA button is no longer available on the requirements type project link screen. (ET does not support updating EA Use Cases so the use case type project link screen will be unaffected). |
JIRA and TFS
Name | Enter a name for the external system that will identify it within Enterprise Tester. |
Enabled | Check this box to enable the connection to the external system. |
| URL | Enter the URL path for the external system. The URL should take the following forms: JIRA: http://URL/rpc/soap/jirasoapservice-v2?wsdl wsdl e.g. http://localhost:8080/rpc/soap/jirasoapservice-v2?wsdl TFS: http://<ServerURL>/<Project Collection> |
UserName | Enter a gateway* username for the external system. |
Password | Enter the password for the gateway username. |
Ignore Remote | Check this box to ignore invalid remote certificates. |
The Gateway Account should be set up as an administration account in JIRA/TFS. This will allow creation, and update of incidents across all projects and will hold sufficient privileges to support enhanced functionality when further integration features are implemented.
...
Name | Enter a name for the external system that will identify it within Enterprise Tester. |
Enabled | Check this box to enable the connection to the external system. |
| URL | Enter the URL path for the external system. This can be left blank is you are working with a non-trial hosted instance of Rally. If you are using a trial hosted version of Rally. The URL is: |
UserName | Enter a gateway username for the external system. This user should have admin permissions and access to all relevant workspaces. |
Password | Enter the password for the gateway username. |
...
The next step is to set up your links between your ET and external projects.
Advanced Settings (JIRA and TFS Connections)
Advance settings allow settings only applies to JIRA and TFS connection. Advance settings allows you to configure which custom fields from your external system will be synchronized with ET. By default, all the custom fields in the defect tracker will be selected for synchronization.
To access the the Advanced Setting Screen screen, from the the Edit External Systems screen screen select the the Advanced Setting button button on the bottom right corner of the screen :
The Advance Setting edit screen will appear. Here Here you can select the custom fields to synchronize. Note Note that if you are chose to custom configure the custom fields to synchronize, you will need to manual manually select any additional custom fields that are added to your external system if you wish to synchronize them. By default, they will not be selected for synchronization. An Enterprise Tester system administrator will need to update this configuration to include the new custom fields for synchronization.
...
Once you have updated the custom field synchronization configuration click click Save and and Close. A Refresh Lookups A refresh lookups will also need to be performed after adding custom fields to the synchronization configuration.
...
For each project in ET that you wish to synchronize with a project in your external system you will need to create a project link. There There are 2 areas where you can create and configure your project links: The links tab of your external system or from the Project Links on the Resources tab Project Links on the Resources tab of the navigator.
External System Links Tab
Once you have created your connection to the external system, click on the the Links tab tab from the Exit the Edit External System Screen screen. Click on on Add from from the tool bar.
The The Add External System Link screen screen will appear. Complete Complete the name and select the the Link Source. This This is the entity type you wish to synchronize only the entity types that are available to your external system type (EA, JIRA, Rally, TFS) will be available for selection.
Once you have selected the the Source, additional fields to configure the ET project and the project will appear.
...
Once you have completed the screen click on on OK. The The External Links Details screen screen will appear. Now Now you will need to complete the field configuration. Please Please see the help topics for the tool you are integrating with. See the end of the page for a list of topic links.
Resources Tab
From the the Resources Tab tab, click to expand "expand Project Links". To view all configured links for your project, double click on your project.
...
To create a new project link select "New" from the toolbar or from the navigator you can right click on your project and select "select Add New Project Link" from 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 '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.
Once the refresh look up completes, the next step is to complete the field configurations. Please Please see the help topics for the tool you are integrating with . See the end of the page for a list of topic linksin the section below.
| Anchor | ||||
|---|---|---|---|---|
|
Listed below are some additional help topics which describe the field configurations required for each External Systemexternal system.
Synchronizing Requirements with JIRA 4- 5.1
...
Synchronizing Incidents with TFS
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 synchronization of the defect tracker. Expand your Configurations folder. Double click on Defect Synchronization Monitor. Here you can check the status of synchronization background task. The Defect Synchronization Monitor displays:
- The current status
- The time of the last synchronization
- The number of items queued for synchronization
From this screen, you can initiate synchronization:
- Synchronize Tickets Now - Synchronize all entities that have been updated or created since the last synchronization.
- Full Synchronize Tickets Now - Synchronize all entities.
- Resynchronize Incidents Now - Synchronize all previously synchronized Incidents.
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 occurred i.e. if a backup of a defect trackers database has occurred, requiring resynchronization of all tickets.