What does an issue look like?
As we have discussed, an issue in JIRA can be anything in the real world to represent a problem domain. It can be a software bug, a help desk ticket, or a customer request. But, what does an issue look like in JIRA? How does JIRA achieve this level of flexibility and still present it in a consistent manner?
Let's first take a look at an issue in JIRA. The following screenshot shows a typical example of an issue and breaks it down into more digestible sections, followed by an explanation of each of the highlighted sections in a table. This view is often called the Issue Summary or the View Issue page:
These sections are described in the following table:
|
Section |
Description |
|---|---|
|
Project / Issue Key |
It shows the project the issue belongs to. The issue key is the unique identifier of the current issue. This section acts as a breadcrumb for easy navigation. |
|
Issue Summary |
It is a brief summary of the issue. |
|
Issue View Options |
These are the various view options... |
