In any issue-tracking system, the issues will be created, then moved to the In Progress state, and finally Closed. This is the scenario of a simple workflow with three states: Open, In Progress, and Closed, which would only work in ideal cases, but in real-world cases, the workflows, that is, how the issue will move from one state to another, could be quite complex. For instance, sometimes you need to wait for some information from the client to act further on the issue; there could be a case when someone will review your task before closing. To incorporate such cases, we need the ability to modify these workflows.
Each company has its own processes and software models. In JIRA, it's possible to customize the workflow very easily. This is one of the most powerful features of JIRA. We can easily create new states and conditions. In this section, we will customize the workflow for a test campaign and a test case.