Mantis glossary

Additional Information – it is the field for information that may be important and/or will bring more clarification. This can be the data related to the bug environment, the link to the screenshot or video.

Attached Files – the block in which the bug confirming file is located (screenshot or video).

• Screenshot – a digital image that shows the contents of a computer or other device display that shows exactly what the user sees. In the screenshot, it is necessary to add a rectangle (highlighting the problem spot) and a red arrow pointed to the bug location. In the case of site testing, the address bar with the site URL must be visible on the screenshot.

Assigned to – the field for the information about the user for whom the task is currently assigned to. The report is assigned to the Training Center if the bug report has been sent for the verification. When the bug report is accepted or it contains errors that need to be fixed, it is assigned to the attendee.

Category –  the drop-down list of categories in the project (they exist for bug reports structuring). The categories for the attendee projects are the homework number / the bug type and facultative assignment. It is not necessary to assign the homework category to bug reports; you can also specify a category according to the bug type (UI, functionality).

Comments – the block where the Training Center specialist comments of the current bug report are displayed after assigning the status. The questions regarding the comments should be asked in the feedback services in the Attendee Personal Account or at the Training Center site.

Date Submitted – the field with information about the date of creation.

Description – i the field for a more detailed description of the summary. It should be described in one sentence using the principle of «What happens? Where does it happen? When does it happen?» according to the summary. You can add maximum 1 more sentence if this is important information and does not fit into the summary due to the characters’ number limit. This field is required.

Edit – the button that opens the page for editing the bug report attributes.

Issue History – the block where there is a history of the changes made to the current bug report and its status, can be found.

ID –  an automatically generated numeric identifier of the bug report. You can use its ID to go to the bug report page by its ID.

Last Update – the field with the date of the last editing.

My View – the section where report lists are displayed sorted by statues: assigned to me, unassigned, reported by me, resolved, recently modified, monitored by me.

• Timeline – the panel on which the history of work and all changes are displayed.

Project – the workspace; f.e.  in Mantis all the tasks exist within a project. A separate project is created for each attendee. The automatically assigned name consists of the group number and surname. Also, attendees are given access to the project with examples of correctly submitted bug reports.

Priority – the drop-down list that allows you to determine how quickly a particular bug needs to be fixed.

• High – the error should be fixed as soon as possible, it is critical for the project.
• Normal – the error is not critical, but requires a mandatory solution.
• Low – the defect is not critical and does not require an urgent solution.

Relationships – it is the block in which the information about the correlation of the reports ties is displayed: parent of, child of, duplicate of, has duplicate, related to. The field indicates the unique identifier of the report with which the bug report is associated.

Resolution – the field in which the defect resolution is displayed; it is either automatically assigned for new bugs, or by the Training Center specialist in other cases.

• Open – is assigned to a new bug report.
• Fixed – the confirmation of the bug correction.
• Unable to reproduce – unable to reproduce the situation with the described data.
• Duplicate – the bug report is a copy of an existing bug report. The report will contain the identifier of the report that is duplicated. This resolution means that a bug report will not be accepted and evaluated.
• Not a bug – a bug report describes a situation that is not an error, the report will be closed with the corresponding comment. This resolution means that a bug report will not be accepted and evaluated.

Reporter – the field that contains automatically filled information about the user who created the bug report.

Reproducibility – it is the drop-down list that allows you to choose the bug appearance frequency under equal conditions. Can be: always, sometimes, random, have not tried, random, unable to reproduce, N/A (not applicable). The default  choice is «Have not tried».

Report Issue – the page for creating a new bug report.

• Issue – a record in Mantis, a bug description, a bug report.

Select profile – it is the drop-down list where you can choose an automatic filling of the bug environment (platform, operating system (OS), version of the operating system (OS Version) from the existing templates. It is possible to manually fill in the environment.

Severity – it is the drop-down list with a list of the criticality degree of the error for the whole system.

• Trivial – is not related to the business logic of the application, a poorly reproducible problem, hardly noticeable through the user interface, the problem of third-party libraries or services, a problem that does not affect the overall quality of the product.
• Text/typo – a small text error / typo. Punctuation or spelling mistake.
• Tweak – it is an inconvenience, an obvious user interface problem. This means that the error needs to be «fit»,  to increase the degree of user interface friendliness.
• Minor – a trivial error that does not break the business logic of the application tested part.
• Major – a significant error, part of the main business logic does not work correctly. The error is not critical or it is possible to work with the tested function using other input points.
• Crash – a critical error, incorrect business key logic, a security hole, a problem that caused the temporary server crash, or made some part of the system inoperable without the possibility of solving the problem using other input points. The solution to the problem is necessary for further work with the key functions of the system under test.
• Blocker – a blocking error that makes the application inoperative, and as a result, the further work with the system under test or its key functions becomes impossible. The solution to the problem is required for the further functioning of the system.

Summary – the title of the bug report. The headline of the bug report shortly and accurately describes the essence of the problem; the «What? Where? When?» principle is used for a standardized approach of the bug summary. The field is required.

Steps to reproduce – the field to describe the sequence of actions that led to the bug in it. The actual and expected results are indicated after the steps to reproduce. Preconditions can be specified before the steps to reproduce.

Status – a status that informs about the checking stage of a bug report.

• Feedback – a bug report needs improvement, contains a comment with notes.
• Assigned – a bug report has been assigned to the Training Center specialists and is awaiting for the verification.
• Accepted – a bug report has been accepted and does not need to be finalized. Such reports are displayed in the block of unresolved estimates.
• Closed – the bug report is closed for the reasons indicated in the comments. This state means that the bug report will not be accepted and estimated. This bug report is not included in the total amount (maximum 50) for the entire course.

Upload files – it is the block where you can upload the file (screenshot or video) for the bug confirming. The system has a size limit for the downloaded files, it is up to 5,000 KB. The screenshot can be added only in the view mode after creating a bug report. The «Upload files» field is absent while editing a bug report.

View Issues –the page that displays a general list of reports; it is possible to filter by various characteristics.