The issue module is one of the most important modules in the project. If you find an imperfection or a deficiency in the application (using test cases), you may record the issue by creating a bug or task. Then the bug can be fixed by the developer or the task can be completed by the assignee.
The template for creating an issue as a bug is divided into groups according to:
- Path to the issue (test plan, sprint and others)
- Priority, assignee and application selection
- Requirement selection
- Basic information about the issue (title, description, attachments and others)
The template for creating the issue as a task is divided into two parts:
- Priority and assignee
- Basic information (title, description)
The main table is divided into two parts. If the issue button is highlighted, you’ll see a list of all the bugs in the projects. After pressing the tasks button you’ll see a table with all tasks and their statuses. The table’s basic functions include:
- Search, filter and table settings
- Create, View, Edit, or Delete an issue
- Group actions
When the bug list table is displayed, you can apply a filter to create a bug group based on the information you select. The second functionality is to set-up a table where you can select only some of the columns to display. You can then export this group to a .xlsx document.
You can use the group actions to change some information about the bugs, such as status, assignee or comment.
When the task list table is displayed, you can apply a filter to create a group of tasks based on the information you select. Once created, the task is added to the Backlog column and the field can be moved to another column.
The last functionality that affects tasks is roll-up. When you click the “-” button, the basic task information will be hidden. Otherwise, the information will appear when you click “+”.
Creating an issue
Before creating any issue, you must select whether you want to create a bug or a task. After filling it in, you’ll see the template. The window is divided into several parts using grey lines:
- The project field is automatically filled with the project where you’re creating the problem.
- After you confirm the project by pressing the select button, the form is displayed. Here you have to fill in all information regarding the problem, its location, type and description.
- The second section contains more detailed information about the issue such as:
- Assign to
- Application, Environment, Module
- The third part is focused on linking with the requirement. If you’ve written the TC according to a requirement, you can link them.
- The last part of the form contains:
- Release number
- Related issues (select the issues associated with the issue you’re creating)
- Description of the issue
- File manager – select the file associated with the issue
Showing & Editing an issue
Click the “Show” button to open a new window. Here you can change status, assignee, add description or related issues. The function of this window is to display detailed information about the error.
The edit buttons shows a similar window, here you can change almost all the issue information.
Creating and editing tasks
Before displaying the task creation form, you must select the issue type: task. After confirmation, you’ll see a template for task creation. The window is divided into two parts according to the content:
- Priority and assignee
- Basic information such as title and task description
When the task main table is displayed, you can see the edit button for a specific task. The form is the same as when creating it (the fields are filled with current data) and you can change any information.