8.7. Creating Issues

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.6.1, “Issue Management”, and Section 6.1.6.1, “Issue Management” contains instructions on how to add an issue management system to a project.

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-Testmanagement 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, 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.

Save

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

Cancel

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

New

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).

The following fields are available for the Jira issue management system:

Summary

A short summary of the issue.

Issue Type

The type of the issue, e.g. a bug or an improvement.

Priority

The priority of the issue.

Components

The components of the system that are affected, multiple selections are allowed here.

Affected Versions

The version of the system in which the issue appeared, multiple selections are allowed here.

Fixed Versions

The version of the system in which the issue has been fixed. Multiple selections are allowed here.

Due Date

The date when the issue should be fixed.

Description

A longer description of the issue.

Test Environment

A description of the test environment in which the issue occurred.

Jira Issue Page

Figure 8.19. Jira Issue Page


The following fields are available for the Trac issue management system:

Summary

A short summary of the issue.

Issue Type

The type of the issue, e.g. a defect or enhancement.

Importance

The priority of the issue.

Components

The component of the system that is affected.

Version

The version of the system that is affected.

Milestone

The milestone of the system that is affected.

Description

A detailed description of the issue.

Keywords

Keywords for the issue.

Trac Issue Page

Figure 8.20. Trac Issue Page


The following fields are available for the Redmine issue management system:

Summary

A short summary of the issue.

Issue Type

The type of the issue, e.g. a defect or enhancement.

Importance

The priority of the issue.

Assignee

The assignee of the issue.

Version

The version of the system that is affected.

Category

The category of the system that is affected.

Description

A detailed description of the Issue.

Estimated time [hours]

The estimated time in hours for completing the issue.

Redmine Issue Page

Figure 8.21. Redmine Issue Page


The following fields are available for the Bugzilla issue management system:

Summary

A short summary of the issue.

Platform

The platform the issue appears on.

Importance

The priority and type of the issue.

Components

The components of the issue.

Version

The version of the system that is affected.

Milestone

The milestone of the system that is affected.

Description

A detailed description of the issue.

Bugzilla Issue Page

Figure 8.22. Bugzilla Issue Page


The following fields are available for the Mantis issue management system:

Summary

A short summary of the issue.

Reproducibility

The ease of reproduction of the issue.

Importance

The priority and type of the issue.

Version

The version of the system that is affected.

Category

The category of the issue.

Status

The current status of the issue.

Resolution

The current resolution of the issue.

Description

The detailed description of the issue.

Additional Information

A text field for additional information about the issue.

Mantis Issue Page

Figure 8.23. Mantis Issue Page


[Tip] Tip

To change the state of the related test case just activate the Update Test Case State? button and choose the new state from the drop down box.

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.8.1, “Issues by Test Case” for more details.