Before proceeding with the reading of this article, it is recommended that you know the concepts below:

• What status can a task have in the operating module of Stays.net?
  I want to know more...
• How to solve technical tasks?
  I want to know more...

Sometimes, during the operational routine, you will find pending issues that will not be solved, be it limited resources, improper creations and other scenarios.

In these cases, you must cancel the tasks, but in the [Resolution] field, mark one of the options below:

• Duplicate
  Task that was previously created by another team member in your pending issues panel.
• No solution
  Requests that cannot be solved, either because what is asked for does not make sense or because of limited resources, for example.

It is important to mention that in both cases, you will have a [Comment] field to better explain what happened.

Knowing how to correctly categorize these points will give you more accurate indicators in the [All Tasks] menu.

Now that you know how to deal with closing tasks with no solution, how about checking out more information about the operational tools of Stays.net?