Better way to capture distinct Eng and QA estimation on a ticket

We are creating at least one technical task (for engineering) and a QA task (for QA) for every story and bug ticket so that the assignee can add an estimation. Then, that estimation is rolled up on the story/bug ticket and is used in Gantt charts. The duplication of tickets, specifically technical tasks for every bug, is causing more noise and requiring more steps in our process. Is there a better way to do this so that we still get separate estimates from Eng and QA on a story/bug without creating subtasks? The team wants to avoid combining eng and QA estimates in one field. I don't know if two separate fields on one ticket will work on a Gantt chart and be accurate.

1 comment
Official comment


I'm Sergey from the YouTrack team.

By design, if you need to separate estimation entities, YouTrack specifically relies on parent → subtask links. All the built-in time-tracking features also follow this logic, so the parent task's estimation value (the same applies to spent time) is summed automatically based on its subtasks' values. Thus, in general, it's not possible to have multiple estimation fields in an issue and use them in the time-tracking features like Gantt Charts.

Alternatively, you can have one main estimation field that you populate yourself based on custom automation. For example, you can have multiple fields and then automatically sum them into another one. Yet, it requires creating a custom script via a workflow, an automation tool. Basically, you create a script that automates issue-related tasks. If you are not familiar with this functionality, please refer to our tutorial.

If you have any questions, please let me know. 


Please sign in to leave a comment.