Page Comparison

...

• Select Test Object: To define where the issue occurred, you can select a test object which gets linked to the issue directly. If no test object is selected, the issue is displayed under 'No test object defined'.

• Affected Part: If a test object possesses a parts list, an affected part can be selected when the issue is created.

• Category: The issue should be placed in an appropriate category to identify the responsible area, which will allow further analysis later. Depending on the selected category, a user can be automatically deposited.

• Severity: The degree of severity describes the extent or importance of the issue.

  • The default severity levels are stored as A, B, C, where A is the most severe, B is preselected as the default for new issues, and C has the lowest prioritization. Depending on the selected severity level, a due date can be automatically stored. Severity levels can be added, edited and deactivated in the administration area. For more information, see: Issue Severities

• Assigned to: The assigned user will see the issue in his tasks and can edit, reassign and resolve it if he has the permissions.

  • If the issue is assigned to a person who does not have the appropriate rights, the error message "This user is restricted and won't have access to the issue" appears. This is the case when the user is restricted to other than the selected test object or has no permissions to edit issues.

• Due Date: The date and time indicate until when the issue should be resolved. If the date is exceeded, the status of the issue changes to 'Overdue'.

  • The due date depends on the selected severity level and is stored automatically. A manual change is possible.

• Title: The title should represent the issue as clear and compact as possible. Later you can refer to a title to search for certain issues.

• Description: The description should include the reason for the issue and any other important information.Category: The issue should be placed in an appropriate category to identify the responsible area which later allows for further analysis.

  Severity: The degree of severity describes the extent or importance of the issue.

  The default severity levels are stored as A, B, C, where A is the most severe, B is preselected as the default for new issues, and C has the lowest prioritization. Severity levels can be added, edited, and disabled through the administration area. For more information, see: Issue Severities

• Taking and Editing Photos: In the lower right corner photos can be added to the issue via the camera icon to document or describe it in greater detail.

• Custom Fields: If the test object for which the issue is created has custom fields, further information can be provided when creating the issue.

...