...
The configuration is performed by the Parasoft administrator and only needs to be set up once. Developers, testers, and other DTP end users should review the Usage section for instructions on how to use Parasoft with Jira.
| Anchor | ||||
|---|---|---|---|---|
|
- Choose Report Center Settings from the settings (gear icon) drop-down menu.
- Choose External Application and choose Jira from the Application Type drop-down menu.
- Enable the Enabled option.
- Enter a name for the server in the Name field. The name is required but does not affect the connection settings or render in any other interfaces.
- Enter the URL of your Jira system in the Application URL field. The URL should include the protocol, host, and port number. Do not include paths or parameters, e.g.,
http://jira.yourcompany.com:8080. - Enter a URL for rendering links to your Jira system from DTP in the Display URL field. This URL should include additional paths that may be necessary to access Jira in a browser, e.g.,
http://jira.yourcompany.com. - Enter your username and either a password (self-managed Jira server) or an API token (Jira Cloud) in the appropriate fields. The login must have sufficient privileges to create Jira issues in the projects specified in the Project Associations section.
- Click Test Connection to verify your settings and click Save.
| Anchor | ||||
|---|---|---|---|---|
|
Xray is an extension for Jira that manages tests. Xray is available as a hosted or cloud-based application. DTP can send data to hosted instances of Xray through the connection as described in Connecting DTP to Jira. For cloud-based instances of Xray, enable the Xray (Cloud) enabled option and specify the Xray client ID and secret so that you can leverage the functionality described in the Sending results from DTP to JIRA/Xray section.
...
Refer to the Xray documentation for information about generating client IDs and secrets: https://confluence.xpand-it.com/display/XRAYCLOUD/Global+Settings%3A+API+Keys
| Anchor | ||||
|---|---|---|---|---|
|
Create links between Parasoft and Jira projects so that defects created in the Violations or Test Explorer view are created in the correct project in JIra. The association is also important when using the the Sending Test Data to External Application flow.
...
You can associate multiple projects in DTP with a project in Jira, but you cannot associate the same DTP project with more than one Jira project.
| Anchor | ||||
|---|---|---|---|---|
|
You can configure DTP to generate widgets and reports that help you demonstrate traceability between the requirements stored in Jira and the test, static analysis, and build review data sent to DTP from Parasoft tools (C/C++test, dotTEST, Jtest, SOAtest).
...
Use DTP Extension Designer to deploy the External Application Traceability Report and the Sending Test Data to External Application flow to your environment. Verify that DTP is connected Jira as described in Connecting DTP to Jira before deploying the artifact.
| Anchor | ||||
|---|---|---|---|---|
|
The first step is to install the Traceability Pack artifact. The artifact is a collection of configuration files and assets that enable traceability.
- Choose Extension Designer from the settings menu (gear icon).
- Click the Configuration tab to open Artifact Manager.
- Click Upload Artifact and browse for the traceability-pack-<version>.zip archive (also see Downloading and Installing Artifacts).
- Click Install and a collection of assets and configuration files for enabling traceability will be installed.
| Anchor | ||||
|---|---|---|---|---|
|
Deploy the report components to your DTP environment after installing the External Application Traceability Report artifact.
...
Deploying the External Application Traceability Report adds new widgets to Report Center, as well as a drill-down report. See Viewing the Traceability Report for instructions on adding the widgets and viewing the report.
| Anchor | ||||
|---|---|---|---|---|
|
This artifact sends test data to Jira when DTP Data Collector retrieves test results from a Parasoft tool. This artifact ships with the Traceability Pack, which must be installed as described in Installing the Traceability Pack before deploying the flow.
- Open Extension Designer and click on the Services tab.
- Choose an existing service to deploy the artifact or create a new service in the DTP Workflows category. Refer to Working with Services for additional information on organizing services and artifacts.
- If you are adding the artifact to an existing service, add a new Flow tab (see Working with Flows) and choose Import> Library> Workflows> Traceability Pack> Sending Test Data to External Application from the vertical ellipses menu.
- Click inside the Flow tab to drop the nodes into the service and click Deploy.
| Anchor | ||||
|---|---|---|---|---|
|
You can modify the ExternalAppsSettings.properties configuration file located in the <DTP_DATA_DIR>/conf directory to change the default behavior of the integration. DTP's out-of-the-box integration with Jira/Xray is configured to use default or commonly-used fields and types. If you customized your Jira/Xray system, however, then you can configure the following settings to align data in DTP with your custom Jira/Xray configuration.
...
| jiraIssueUrl | Specifies the URL template for linking work items created in the DTP Violation Explorer and Test Explorer to work items in Jira. Default:
The value of the <JIRA_URL> segment of the URL path is specified when connecting DTP to Jira. See Connecting DTP to Jira. | ||||||
|---|---|---|---|---|---|---|---|
| jira.issueType.bug | Specifies the name for the issue type in Jira that takes the role of bugs when creating work items from the DTP Violations Explorer and Test Explorer. By default, the property is not set. As a result, bug work items created in DTP are associated with bug work items in Jira. | ||||||
| jira.issueType.task | Specifies the name for the issue type in Jira that takes the role of tasks when creating work items from the DTP Violations Explorer and Test Explorer. By default, the property is not set. As a result, task work items created in DTP are associated with task work items in Jira. | ||||||
| jira.issueType.test | Specifies the name for the issue type in Jira that takes the role of tests. When test results are sent from DTP to Jira/Xray, tests will be labeled as the issue type specified in this setting. Default:
This setting can be used in on-premise and cloud-based instances of Jira/Xray. | ||||||
| jira.issueType.requirement | Specifies the name for the issue type in Jira that takes the role of requirements. When test results are sent from DTP to Jira/Xray, the requirements associated with the tests will be labeled as the issue type specified in this setting. The issue type is also used to identify requirements in the Traceability Report. Default:
This setting can be used in on-premise and cloud-based instances of Jira/Xray. | ||||||
| jira.testDone.transitionId | Specifies a custom status for tests sent from DTP to Jira/Xray. If not specified, the default system status for completed tests is used. See Getting Default Test and Test Execution Statuses for information about getting the default test status names used in your system. | ||||||
| jira.testExecutionDone.transitionId | Specifies a custom status for test executions sent from DTP to Jira/Xray. If not specified, the default system status for test executions is used. See Getting Default Test and Test Execution Statuses for information about getting the test execution status names used in your system. | ||||||
jira.testType.customfieldId
| Specifies the ID of the test type custom field in your Identifies the field that sets the test type for tests created when results are sent from DTP to Jira/Xray system. When the field is identified, tests are The value should match the existing custom field. Tests will be labeled according to the type specified with the the jira.testType.customfieldValue setting setting. Setting this value does create the custom field; the value should match the existing custom field in your Jira/Xray system. If left empty, the default value Both the By default, both See See Getting Values for Custom Test Type Fields for additional details. This setting can be used in on-premise and cloud-based instances of Jira/Xray. | ||||||
jira.testType. customfieldValue
| Specifies which test type is assigned to Identifies the test type to assign to tests created when results are sent from DTP to Jira/Xray. Setting this value does create the custom test type value; the The value should match the existing custom field in your Jira/Xray system. If left empty, the default value is used. This setting is empty by default.in your Jira/Xray system. The custom value is identified by the ID specified in with the Both the By default, both See Getting Values for Custom Test Type Fields for additional details. This setting can be used in on-premise and cloud-based instances of Jira/Xray. | ||||||
| jira.xrayOnPremises.testCaseFindingStatus.pass | Specifies the test run status name in Jira/Xray to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in on-premise instances of Jira/Xray. | ||||||
| jira.xrayOnPremises.testCaseFindingStatus.fail | Specifies the test run status name in Jira/Xray to assign to failed test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in on-premise instances of Jira/Xray. | ||||||
| jira.xrayOnPremises.testCaseFindingStatus.incomplete | Specifies the test run status name in Jira/Xray to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in on-premise instances of Jira/Xray. | ||||||
| jira.xrayOnPremises.testToRequirementRelationName | Specifies the name of the requirement type in Jira for tests sent from DTP. This enables you to associate tests with requirements using a custom name you may have configured in Jira. Default:
This setting can be used in on-premise instances of Jira/Xray. | ||||||
| jira.xrayCloud.testCaseFindingStatus.pass | Specifies the test run status name in Jira/Xray to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in Cloud instances of Jira/Xray. | ||||||
| jira.xrayCloud.testCaseFindingStatus.fail | Specifies the test run status name in Jira/Xray to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in Cloud instances of Jira/Xray. | ||||||
| jira.xrayCloud.testCaseFindingStatus.incomplete | Specifies the test run status name in Jira/Xray to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in Jira for test results in DTP. Default:
This setting can be used in Cloud instances of Jira/Xray. | ||||||
| jira.xrayCloud.testToRequirementRelationName | Specifies the name of the requirement type in Jira for tests sent from DTP. This enables you to associate tests with requirements using a custom name you may have configured in Jira. Default:
This setting can be used in Cloud instances of Jira/Xray. |
...
- See Creating an Issue in a Third-party System for instructions on how to manually create bugs and tasks in Jira from the Violations Explorer view.
- See Creating an Issue in a Third-party System for instructions on how to manually create bugs and tasks in Jira from the Test Explorer view.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The following diagram shows how you could implement an automated infrastructure for integrating Parasoft DTP and Parasoft test execution tools into your Jira environment:
...
You can also drill into test executions associated with the test.
| Anchor | ||||
|---|---|---|---|---|
|
If the External Application Traceability Report has been deployed to your system (see Enabling the Requirements Traceability Report), you can add widgets to your dashboard to monitor traceability from requirements to tests, static analysis, code reviews for your project. The widgets also drill down to a report that includes additional details.
...