JIRA Workflow for DevOps and QA

Workflow is a set of activities used to track the status and transition of a problem during its life cycle.
When the problem shifts from one state to another, the transition represents some work in the form of a connection between the two states.

Status: The status determines the impact of the tester’s questions.

In the Jira tool, the following are the stages that occur in the workflow:

All status
In progress
finished condition
JIRA workflow

Two activities were performed in the TODO state:
Problem creation When testers find defects, they record the defects in the Jira tool. Once the defect is recorded in the Jira tool, the unique ticket identification number will be generated by the Jira tool. This process is called problem creation.
Summary and other detailed information Problem creation requires some additional information that needs to be added or updated to the problem, such as problem description, priority, severity, affected components, subtasks, upload screenshots, email history, etc. After adding all the details to the question, the Jira tool will assign the status to TODO status.
Three activities were performed in the "in progress" state:

After the assignee creates the problem, it assigns it to an individual or team. After the problem is assigned to the person, the status will change to "in progress" status.
The work review is first carried out by the problem reporter, the assignee and other project managers to review and monitor the work on the related issues. When a developer deletes a problem, the developer must first unit test it, and then the code review team will review it. During the work review activity, the status remains "in progress".
After the quality analysis code is reviewed, the changes will be verified by the quality analysis team, including regression testing. If the QA team finds any problems in the change, it will reassign the problem to the developer, otherwise the QA team will close the problem and indicate that the problem has been resolved. During the quality analysis, the status remains "in progress".
Perform an activity in the "completed" state:

Once the product is put into production, it will be released on the market once it has been developed and tested. When the product is released on the market, the status will change to the "complete" status.
The JIRA workflow can also be called the defect life cycle. The defect life cycle is as follows:

JIRA workflow
Unresolved issues: After the issue is created, the issue is assigned to the software developer, and they begin to work on it.
Problem in processing: The software developer started to deal with the problem.
Resolved issue: The issue has been resolved by the software developer, but is waiting for verification by the tester. If the verification is successful, the problem has been solved; otherwise, the problem will be reopened.
The problem of reopening: If the software developer does not solve the problem according to the requirements, the problem enters the state of reopening.
End problem: When the software developer correctly solves the problem and is verified by the software tester, the problem will be solved.