Product assembly and testing tasks

[Mehran Moss]

We are starting to use Jira Core and Software for our product builds and tests.
I'm working in an engineering environment where I create individual projects for every sales order we have.
This project follows our specific workflow created, starting from initial design, drafting, material procurement, assembly and testing.
I create project issues for every stage (Assembly or Testing) in the project and assign different groups to it.
I use Epics to group issues related to Assembly or Testing.
Then use Kanvan boards to keep track of issues and Epics, in the project. In this was Epics are higher level tasks. Say Order1 Initial Testing is an Epic with sub tasks as Test Cables, Test Circuit, DC Test , RF Test, etc
Is this a right way to use Epics in this I stance?

[Arthur Gonçalves · Accepted solution]

Hi Mehran,

If we stick to the literal definition of an Epic based on scrum methodology, then it could be questionable to use Epics as a simple grouping mechanism. There are other options (like using custom fields or labels) to order issues between different stages.

However, the concept of right or wrong is pretty relative on this scenario and therefore you can use it as described without any problems. To be honest, I actually use Epics to organize different categories of tasks for some personal projects which are independent of other team members and that work for me.

Hope this helps! :) 

Regards,
Arthur Gonçalves | Atlassian Support

[Mehran Moss]

Thanks, that answered my question!