Build a logical flowchart for working with MeisterTask?

Question

block diagram

Good evening, please help me build a logical block diagram for working with MeisterTask Task
life cycle in MeisterTask
Backlog. Contains tasks discussed with the customer or pending discussion. During a meetup, tasks are randomly added to this column by the product manager. They are then sorted by execution priority.
hold. Tasks go to this block if they were planned, but for some reason they will not be performed (lack of funds, time, employees, etc.). Contains frozen tasks (put on hold).
estimate. In this column from the backlog, the tasks approved by the customer are evaluated. At this stage, the task performer, its observer, due date and tags are assigned. In the task dialog, under its title, the time in hours required for its execution is indicated. Before you start a task, you must press the "start" button to account for the actual amount of time spent on the current task.
in process. Tasks fall into this block only after the Estimate column. Here are the tasks that are being worked on at the current time.
Done. The task can be moved to this block after the complete completion of work on it in the in process column. Tasks in this column are considered completed and are pending testing.
test. This column contains tasks from the Done block that are currently undergoing testing.
Approved. This column contains fully completed tasks that have passed the testing stage.
Done, but not used. Contains completed tasks that were not subsequently requested.

Answer 1

I have never drawn a block diagram, but then the teacher asked me to do it, all hope is on you!