Jira: one big workflow or several different ones?

Question

Project management

There is a task in the process: development of the database, front-end, back, testing and acceptance and deployment. + writing an auto-test.
How to organize it correctly?
Because backend and front and DB are made by different people - most likely, subtasks are needed for the task. But testers should test the resulting finished task and pour it out.
I would like to designate the task - to see it again in the completion stage - without controlling all the transitions of the steps.
How are you doing?
Is each transition a separate task? Or a big workflow?
Should the pour be framed as a step?

Answer 1

There are many options:
1. Use sub-tasks
2. Use links between tasks
3. Versions and/or components

Answer 2

Divide into categories (database, layout, etc.).
Use scrum (Ideas, tasks for the week, in progress, testing, bugs, completed)
In this option, testers will have their own task of testing the entire module. After which they will describe the bugs. Then you (or the tester himself) write bugs for each development department (the task is again transferred to the "in progress" status with notes about bugs.

Answer 3

You can see the info in this blog, here is an interesting article about Jira workflow: https://polontech.com/ru/blog/advanced-jira-workfl...