...
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 entity type in Jira that DTP treats as requirements. DTP will present Jira entities specified with this setting in traceability widgets and reports. When sending test results from DTP to Jira/Xray, DTP will update or create test cases for the entities specified with this setting that match the IDs specified with the 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 Jira/Xray system. The value should match the existing custom field. Tests will be Identifies the field that sets the test type for tests created when results are sent from DTP to Jira/Xray. When the field is identified, tests are 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 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 tests 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.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. |
...