8.7. Creating Issues

8.7.1. Creating a Bugzilla Issue
8.7.2. Creating a GitHub Issue
8.7.3. Creating a GitLab Issue
8.7.4. Creating a Jira Issue
8.7.5. Creating a Mantis Issue
8.7.6. Creating a Redmine Issue
8.7.7. Creating a Trac Issue

After the execution of a test case or test suite has been finished, an issue in an issue management system can be created. In order to do this, at least one issue management system has to be configured and also available in the selected project. The configuration of an issue management system is described in Section 10.5.1, “Issue Management Settings”, and Section, “Issue Management” contains instructions on how to add an issue management system to a project.

It is also possible to link or create an issue during the test execution. To link a issue during the test execution the must be clicked. To create an issue the icon must be clicked to open the Create Issue page.

Clicking on the Create Issue button on the results page which is displayed after the execution of a test case or test suite opens the Create Issue page.

By default, the system uses the credentials entered at the login screen to authenticate the user against the issue management system. If the credentials entered at login do not work, and the issue management system has not yet been used during the session, Klaros-Test­management will request new authentication information in a dialog.

The content of the Issue Management page is mostly dependent on the issue management system in use and its capabilities and configured custom fields, but all of the pages for the various issue management systems have some elements in common:

Issue Management System

When there are more than one issue management systems configured for the project, the issue management system where the new issue will be created can be selected in the issue management system drop-down field.


The Save button creates or updates an issue in the selected issue management system.


The Back button discards unsaved changes and directs the user back to the test execution.


After an issue has been saved, an additional New button is provided to allow the creation of more than one issue (e.g. in another issue management system).

[Tip] Tip

To set the state of the related test case to Blocked select the Update Test Case State? button.

For more detailed information about each field, please consult the documentation of the respective issue management system.

The created issues can be inspected in the Issues by Test Case page of the Evaluate section see Section 9.13, “Issues by Test Case” for more details.

8.7.1. Creating a Bugzilla Issue

the “Bugzilla Issue ” Page

Figure 8.18.  the Bugzilla Issue Page

8.7.2. Creating a GitHub Issue

The “GiHub Issue” Page

Figure 8.19.  The GiHub Issue Page

8.7.3. Creating a GitLab Issue

The “GitLab Issue” Page

Figure 8.20.  The GitLab Issue Page

8.7.4. Creating a Jira Issue

The “Jira Issue” Page

Figure 8.21.  The Jira Issue Page

8.7.5. Creating a Mantis Issue

The “Mantis Issue ” Page

Figure 8.22.  The Mantis Issue Page

8.7.6. Creating a Redmine Issue

The “Redmine Issue” Page

Figure 8.23.  The Redmine Issue Page

8.7.7. Creating a Trac Issue

The “Trac Issue” Page

Figure 8.24.  The Trac Issue Page