Jira: one big workflow or several different?

In the process there is a task: development of database, front-end, Beck, test and acceptance and deployment. + writing auto test.

How to organize it correctly?

Because the backend and front and DB do different people - likely to fit under.task to task. But testers have to test the resulting task and ready to pour.

I would like denoting task - to see her again in the stage of completion is not controlling all of the navigation steps.
How do you do?
Each transition a separate task? Or a large workflow?

Whether the heat is provided with ready to make a step?
July 4th 19 at 23:08
2 answers
July 4th 19 at 23:10
There are many options:
1. To use sub-tasks
2. To use links between tasks
3. Version and/or components
July 4th 19 at 23:12
To separate into categories(database, layout, etc.).

Use scrum (Ideas, tasks for the week, working, testing, bugs, implemented)

In this embodiment, the testers will have a task of testing a whole module. After which they describe bugs. Then you(or the tester) painted bugs for each development Department(problem is again transferred to the status "in progress" with notes about the bugs.

Find more questions by tags JIRAProject management