# Task Perspective

In the Task perspective, you can create tasks to keep track of the progress of the removal of findings and quality deficits. It is possible to assign tasks to a user and annotate them with tags for filtering. Tasks can be in different states to reflect the progress of the work.

# Tasks Overview View

As default the Task perspective shows a table of all open tasks. The table shows the most important information of the tasks and is sortable by clicking onto the header.

Tasks Overview

Large software systems can have many tasks. To better navigate them, the sidebar provides several filter mechanisms. The tasks can be filtered by their task states or by different tags. Additionally, it is possible to filter them by their author or assignee:

Image: task-filter

# Create Task View

There are two ways to create a new task, either by attaching a finding to a new task, or by clicking on the New task button above the filters. If you create a task via the button New task, the Create Task View opens:

Task Create View

A task must have a subject that briefly describes the purpose of the task. Additional you can set an assignee and annotate it with some tags, e.g., urgent. The description can be used to clarify the intent of the task and give hints to resolve it. It is possible to format the description with markdown, for help you can click on Formatting below the label Description. It is possible to attach findings after the creation of the task via the Findings or Code perspective.

The Edit Task View allows you to edit the fields of an existing task.

# Action: Edit Tasks

Within the Edit Task View it is possible to change the field values you have set during the creation of a task. In addition, it is possible to set the state and resolution of a task and remove the findings from the task by clicking on the symbol.

Image: task-edit

The changes are stored in the change history of the task:

Image: task-history

# Task Details View

The Task Detail View shows all details of a task and allows you to work on it. This means you can change the state of a task or you can discuss a solution to resolve it.

# Action: Work On Tasks

A task can be in one of the following four different states:

  • Open An unresolved task.

  • Ready for review The task has been resolved by the assignee.

  • Closed A quality engineer has confirmed the resolution.

  • Discarded The task has been discarded.

Throughout the normal workflow a task starts with the status Open . The assignee addresses the problem in the code and changes the status to Ready for review . This gives the quality engineer the opportunity to verify the solution. He can then either set the status to Closed , if the solution is valid or again to Open , if there are still problems.

The resolution gives a hint to the quality engineer how the task was tackled: either it was fixed or it was not possible to fix it for specific reasons.

Image: task-detail

If you want to reference a specific Teamscale task from a commit, you can add TS\#<ID> to the commit message. The <ID> notes the ID of a specific task, e.g., TS\#3. This commit is then referenced in the Task Detail View:

Image: task-commit

It is possible to discuss a task within the Task Detail View this can be used to clarify the description or a solution:

Image: task-discussion