Best practice workflow for time estimation and task break down(Dev -> QA -> Done)

[Aviad Hadida]

Hi all.. We are trying to achieve a decent workflow that will allow us to use time estimations along with tasks break down.

We have 2 types of tasks / Issues:

1. Isolated issues - Only require one person. Like fix bug / New feature on the UI or fix bug / New feature on the Server

2. Combined - Require backend and UI change

We want to estimate the work and see the sum of it on the Jira backlog / board.

One way to work is an epic with stories for each person. 1 story for backend, one story for front end and one for QA. That way we can assign task to every person in the chain and we can see time tracking

Pros: 
- We will be able to estimate per person

Cons:
- The QA doesn't see it in the board as task completed and needs to have a QA. He needs to understand from the team if all stories are finished

Another way is subtasks but they cannot sum in the backlog..

So what the hell is the best practice to achieve that?
Our board looks like that:


On every path i tried to go something came up..

I am not newbie on Jira but in every company i worked it was the same complex and un resolved workflow

Anyone can help me here? Tried to watch endlessly videos on you tube from Attalsain but couldn't find even 1 example

[Jillian Amyot _Unito_]

Hey @Aviad Hadida , if you're passing off issues to other teams, you might find Unito helpful! It has live sync between tools so your projects move from one team and passed off to the next. If you want to better your workflow, they have a launch called workflows coming soon that sounds like it would help you visualize and map your workflow. Hope this helps!

[Aviad Hadida]

Thanks but this is not what we need.. I am talking about a basic workflow with one project that will require time estimation and how to create issues in a way that we can track times and to break down tasks for different people