QA & Developers & Tempo App time tracking

[Tony Qumsieh]

as an software programming company using Agile Scrum . 

Our workflow as following : 

we are using the Projects As Customer Name , And the Epics as the Projects inside this customer , So let say we have epic name  Epic-2.1.1  then the developer starts with task in this epic  , when finish it , he/she then Re-assign the Task to QA team for testing  , the QA Lead Opens another epic Related to the Epic 2.1.1 name Epic QA : 2.1.1 , and the QA team testing it on this epic , if they find Bugs , they open the Bugs in the Main Project Epic Epic-2.1.1  , so the programmer works On it 

why we are doing this ? 

because we are using the Tempo Timesheet time Tracking app + Planning From tempo , and We did this because we don't want the Programmer and the QA Employee Log time in the same Bug , Because we gave the Bug Original Estimate , And We need each bug or Issue to let Only 1 Employee To work on it . to track the time Correctly 

what is my Question ? 

what is the Best Practice to make the flow for our company that have a lot of epics and many programmers + QA team  , with flow Epic , Task , Bug , Sub-Bug , Test , Sub-test with different employees working on it . 

[Brant Schroeder]

@Tony Qumsieh Welcome to the Atlassian community

I would suggest doing the following:

Epic 2.1.1 - Have the following sub Epics

- Epic 2.1.1 Development
- - Bug
- - Bug
- Epic 2.1.1 QA

You could also use Stories under the epic for development, QA, etc.