Priority of the executor for fixing the defect

Prioritization when choosing a performer to fix a defect:

To select the most suitable performer for defect resolution, the system indicates a connection between the defect and an existing Task (or Solution Item or Epic). In other words, the user can specify the preferred "path" for choosing the performer.

Impact on Assigning Executors

The connections of a defect play a crucial role in assigning the right person to fix it:

• If the task that introduced the defect is known: Priority is given to the person who worked on that task. This approach is based on the fact that the person who introduced the defect best understands the problem's context. However, the priority may be adjusted if fixing the defect requires higher skills (e.g., senior-level expertise).

• If the defect is linked to a Solution Item: Executors who worked on tasks within that Solution Item are considered first. However, only those who were directly involved in creating the element are considered.

• If the defect is linked to an Epic: Priority is given to all executors involved in the epic's work, even if their contribution was indirect.

Rules for establishing connections between a defect and other tasks:

For Task:

✅ A connection can be established with any task if it is at stages from In progress (has gone through this stage at least once) to Done, both in closed projects or projects on hold and in the state not defined. That is if work on the task is ongoing or has been carried out and was interrupted for any reason.

For Solution Item:

✅ A connection can be established with any solution if it has tasks at stages from In progress (has gone through this stage at least once) to Done, both in closed projects or projects on hold and in the state not defined.

For Epic:

✅ A connection can be established with any epic if it has tasks at stages from In progress (has gone through this stage at least once) to Done, both in closed projects or projects on hold and in the state not defined.