Configuring the integration of DTP with Jama Connect is performed by the Parasoft administrator and only needs to be done once.
In this section:
Connecting DTP to Jama Connect
- Choose Report Center Settings from the Settings menu (gear icon).
- Choose External System, click Edit Settings, and choose Jama Connect from the System type menu.
- Enable the Enabled option.
- Enter a name for your instance of Jama Connect in the Name field. The name is required but does not affect the connection settings or render in any other interfaces.
- Enter the URL for the Jama Connect server in the Application URL field. The URL should include the protocol, host, and port number. Do not include paths or parameters.
- The Display URL field defines the URL which is displayed in Parasoft DTP pages when links to your Jama Connect system are presented in a web browser. Typically, this should be the same as the above Application URL field. However, it might be different, for example, when you work in a reverse proxy environment and links to Jama Connect from the user's local web browser with Parasoft DTP are different than from the Parasoft DTP server.
- Enter login credentials in the Username and Password/API token fields. The login must have sufficient privileges to create issues in the Jama Connect projects specified in the Project Associations section.
- Click Test Connection to verify your settings and click Confirm.
Associating Parasoft Projects with Jama Connect Projects
Associating a Parasoft project with a Jama Connect project allows you to create defects from the Violations or Test Explorer views that are linked to the correct project in Jama Connect. The association is also important when using the Sending Test Data to External System flow. You can associate multiple projects in DTP with a project in Jama Connect, but you cannot associate the same DTP project with more than one Jama Connect project.
- Click Create Project Association and choose a project from the DTP Project menu in the overlay.
- Enter the name of a Jama Connect project in the External Project field and click Create to save the association.
Click the trash icon to remove a project association. Deleting the project association does not remove links from DTP explorer views to defects in Jama Connect. If an association is deleted and recreated later, existing links between violations and Jama Connect issues will be reactivated.
You can reconfigure an existing association between DTP and Jama Connect projects:
- Click the pencil icon and choose either a different DTP project from the menu or specify the name of a different Jama Connect project in the External Project field.
- Click Save.
Advanced Configuration
You can modify the ExternalSystemSettings.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 Jama Connect is configured to use default or commonly used fields and work item types. If you customized your Jama Connect system, however, then you can configure the settings detailed below to align data in DTP with your custom configuration.
Please note that ExternalSystemSettings.properties is expected to use ISO 8859-1 (Latin1) character encoding. Any character not supported by ISO 8859-1 must be represented in keys and elements using Unicode escape sequences, which is to say a backslash (\) and a lowercase u, followed by the four-digit hexadecimal code for the character. For example, the "En Dash" (–) character (not to be confused with the "Hyphen-Minus" character (-)) is not supported by ISO 8859-1, so it must be represented by its Unicode escape sequence \u2013. As a result, something like example.property.value=Foo – Bar would need to be entered as example.property.value=Foo \u2013 Bar.
| jamaIssueUrl | Specifies the URL template for linking items created in the DTP Violation Explorer and Test Explorer to items in Jama Connect. Default:
|
|---|---|
jama.item.types.to.skip | Specifies a list of item types that are not related to Sets of Requirements in a Jama project. Used in Parasoft C/C++ and SOAtest Requirements View to present Jama test cases associated with Jama requirements. Default: jama.item.types.to.skip=BUG;SET;TXT;FLD;TC;LTC;HTC;VALTC |
| jama.bugSet.name | Specifies the name of a set of defects in Jama Connect where new defects will be added or where existing defects will be updated when defects are created from the Parasoft DTP Violation and Test Explorer views. If the set of defects does not yet exist, it will be created and given the name specified in this property. Default:
|
| jama.sync.testcase.relationship.type | Specifies the relationship type between requirements and test cases used for creating a new test case during the sending of test results from DTP to Jama. If not set, the default relation type in Jama is set. Default: jama.sync.testcase.relationship.type=Verified By |
| jama.testcase.relationship.types | Specifies a list of relationship types used to filter appropriate test cases related to requirements. The values should be a list of relationship types names separated with ";". If the setting has no specified values, all of the relationship types available in Jama system will be used. Used in Parasoft C/C++ and SOAtest Requirements View to present Jama test cases associated with Jama requirements. Value: jama.testcase.relationship.types=Verified by;Validated by |
| jama.testcase.types | Specifies list of item types related to Sets of Test Cases in Jama project. The values should be a list of keys separated by ";". Used in Parasoft C/C++ and SOAtest Requirements View to present Jama test cases associated with Jama requirements. Also used while synchronizing DTP data with Jama when adding new Test Cases. Default: jama.testcase.types=TC;LTC;HTC;VALTC |
