On the Integration page, external systems are connected and their settings are managed. It features six tabs, Issue Management, Requirements Management, E-Mail, Network, LDAP and CAS.
An issue management system (also called issue tracker or bug tracker) is an application for managing issues that occur during the testing process. Issues can contain information and reports about errors in a software system.
Issues can be created in issue management systems, retrieved and assigned to failed test case results. It is possible to configure and use multiple issue management systems simultaneously.
Klaros-Testmanagement supports the following issue management systems:
|External Configuration Required|
Some issue management systems need to be configured before they can be successfully connected to Klaros-Testmanagement. For more information, see Section 3.14, “Configuring External Issue Management Systems”.
|Token based authentication|
Some issue management systems like Jira, GitHub or GitLab restrict access to token-based authentication. Authentication via username and password is not supported.
Klaros-Testmanagement is supporting a token based authentication scheme as well. Just use the required username and the token as password.
The table shows the following values:
A tooltip appears when the cursor is placed over the icon shown here.
no credentials for background synchronization has been provided.
|The used issue management system (Bugzilla, Jira (Version 4.3 or higher), Jira Legacy (Version 4.2 or lower), GitHub, GitLab, Mantis, Redmine and Trac).|
|The link to the issue management system.|
|See Section 10.5.1.4, “Project”.|
|A short description of the issue management system.|
|The executable actions.|
By clicking on the buttona new empty table row will appear. All attributes of the issue management system can be defined here.
Withthe issue management system saved. The ID of the issue management system (IM00001) is automatically assigned by Klaros-Testmanagement.
Withseveral table rows can be created and edited at the same time. Only when clicking on the data is stored in the database.
Withall changes are undone.
All rows with red IDs have been changed and are not yet saved!
The following actions can be performed in the action column:
The following operations can be performed in the line above the table on the right:
All operations are described in detail in Section 126.96.36.199, “Overview Page”.
If the issue management system organizes issues in projects, a project ID is required to address the specific project. Jira, Redmine, Mantis and Bugzilla use such a project id. With GitHub, GitLab, and Trac, the URL is used to address different projects.
The valid project ID values can be found in the issue management systems at the following locations:
The Bugzilla project id consists of the
Product field value.
The Jira project id consists of the
Key field value.
The Mantis project id consists of the
Project Name field value.
In the Action column, click the icon to check whether a connection to the issue management system can be established.
|Trailing Slashes of URLs|
In case of an authentication error, first check whether the addition or deletion of a trailing slash to the URL resolves the problem.
Clicking on the icon in the action column on the right opens a dialog. The credentials for the background synchronization can be provided here. In addition, the status values for fixed issues are defined here.
The credentials entered here will solely be used for background synchronization. If users creates or updates an issue, their personal credentials will be used to authenticate against the issue management system. If credentials are missing or not valid, then users are prompted to enter them.
Each issue has a status field that documents its current state (e.g. "In progress" or "Fixed"). The individual statuses and their naming vary according to the issue management system used. Klaros-Testmanagement only distinguishes between open and resolved issues. An issue is considered closed when no further work needs to be done on it (e.g. "Closed", "Rejected"), otherwise it is still open.
Resolved issues are displayed in green, open ones in red. Section 9.6.2, “Issues by Test Case Details”
The resolved issue states must be named exactly as they are in the issue management system, otherwise they will not be properly identified and will be counted as open issues.