In Jira, we have default issue types, such as Epic, Story, Task, Sub-task, and Bug. These issue types give us flexibility to define our own issue types as per the project's requirements. However, each of these issue types can be treated as a requirement. Once the requirements are defined and logged in the system, it becomes easy to track and manage them. We learned how to define requirements in Chapter 3, Understanding Components of Testing with Jira. So now, let's create them in Jira.
Jira has a predefined set of fields to create Jira tickets. Additionally, we can add customized fields as required according to the selected issue type. Any requirement issue type should generally contain the following:
- The purpose of the requirement or the task that the team is expected to accomplish
- The detailed description that breaks the complex requirement down into further details and specifications
- The issue type's priority
- The issue type's...