Understanding issues
An issue in Jira usually represents a unit of work that users will work on. Depending on how you are using Jira, an issue can also represent other things and concepts in the real world. For example, in a software development project, an issue can be a bug or a story, while in an IT service project, an issue can be an incident or a support request.
Despite all the differences in what an issue can represent, there are several key aspects that are common to all issues in Jira, listed as follows:
- An issue must belong to a project.
- It must have a type, also known as an issue type, which indicates what the issue represents.
- It must have a summary. The summary acts like a one-line description of what the issue is about.
- It must have a status. A status indicates where along the workflow the issue is at a given time. We will discuss workflows in Chapter 7, Workflow and Business Process.
In summary, an issue in Jira represents a unit of work...
