Add Issue

Issues can be recorded both in the task menu and during the completion of a checklist. By selecting “Add issue“ the issue will not be related with a checklist.

Various properties can be defined to describe and categorize the issues. By selecting the “save” button the issue gets created.

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: https://testify.atlassian.net/wiki/spaces/TWN/pages/2452783191
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.
Adding and editing photos and files: In the bottom right-hand corner, the camera icon can be used to add photos and files to the defect in order to document or describe it in more 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.

Based on customers individual processes the default date can be set for the customer. The field "Due date" can be adjusted for the date and "Time of day" can be adjusted for the time until which the issue should be resolved by the "Assidned to" user or group. For this requirement please contact your Testify consultant.

If not all requirements have been met, an overview of all checks that need to be adjusted before completion appears. Clicking on the respective check takes you directly there and allows you to adjust it accordingly so that the restrictions are met. The link is only activated when the device is online, in offline mode there is no link to the check. Example:

Add and edit photos and files

By clicking on the camera icon in the bottom right-hand corner, photos and files can be added to the defect to document or describe it in more detail.

Data size: No compression up to 4MB, automatic compression from 10MB. In between, users can decide for themselves whether the files should be compressed (or not).

Immediately after uploading, the user can use objects and drawings to point out the location of the defect. The photo can also be cut out and rotated as desired.

Once the photo is added, it can be edited by clicking on the color roller in the upper right corner of the photo.

Remove photos

Photos can be removed as well. Removed photos appear grayed out and are listed at the end. This is traceable via the history and can also be reactivated there. Removed photos are not visible in the PDF protocols.

Resolve Issues

See: https://testify.atlassian.net/wiki/spaces/TWN/pages/1577386090/Issue+overview#Resolve-issue

Add an issue within a checklist

https://testify.atlassian.net/wiki/spaces/TWN/pages/1507197212/Execute+checklist#Add-issue