...
Field | Description |
|---|---|
| Type | Select the tracker type from the list of supported trackers. |
| Name | Enter a name for the tracker that will identify it within Enterprise Tester. |
| URL | Enter the URL path for the defect tracker. e.g. JIRA: http://yourjiraserver/rpc/soap/jirasoapservice-v2?wsdl |
| UserName | Enter a gateway* username for the defect tracker. |
| Password | Enter the password for the gateway username. |
| Enabled? | Check this box to enable the connection to the defect tracker. |
| Ignore Invalid Remote Certificates? | Check this box to ignore invalid remote certificates. |
* We recommend that the Gateway Account has JIRA administration accessThe Gateway Account must be assigned to the JIRA Administrators, Developers and Users default groups in JIRA. 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.
...
Upgrading from an existing JIRA configuration that uses the JIRA 4 - 5.1 plugin to use the JIRA plugin (which supports JIRA 5.2 and above) is easy. Provided that you are using JIRA 5.2 or above, you can simply click on the "Upgrade" button on the Edit External System.
This change is reversible. After upgrading, if you decide to move back to the JIRA 4 - 5.1 plugin, you can simply click on the "Downgrade" button:
All of your project links will automatically be upgraded to use the JIRA plugin.