Different organizations use JIRA to track different kinds of issues. Depending on how your organization is using JIRA, an issue could represent a software bug, a project task, a helpdesk ticket, a leave request form, etc.
A JIRA issue typically looks like this (click to enlarge image):
Your JIRA issues may look different to the above screenshot if your administrator has customized JIRA for your organization.
The fields shown in the above screenshot are:
|Project ||The parent project to which the issue belongs. In this case, Angry Nerds.|
|Key||A unique identifier for this issue, in the example above: ANGRY-304. (The characters to the left of the hyphen represent the project to which this issue belongs.)|
|Summary||A brief one-line summary of the issue. For example, "Red Angry Nerd is scary."|
|Type||See below for a.|
|Status||The stage the issue is currently at in its lifecycle (workflow). See below for a .|
|Priority||The importance of the issue in relation to other issues. (See below for a).|
|Resolution||A record of the issue's resolution, if the issue has been resolved or closed. (See below for a list of resolutions).|
|Project version(s) for which the issue is (or was) manifesting.|
|Fix Version(s) |
|Project version(s) in which the issue was (or will be) fixed.|
|Project component(s) to which this issue relates.|
|Labels to which this issue relates.|
|The hardware or software environment to which the issue relates.|
|Description||A detailed description of the issue.|
|Links||A list of links to related issues. (Strikethrough text, |
|Assignee||The person to whom the issue is currently assigned.|
|Reporter||The person who entered the issue into the system.|
|Votes||The number shown indicates how many votes this issue has.|
|Watchers||number shown indicates how many people are watching this issue.|
|The date by which this issue is scheduled to be completed.|
|Created||The time and date on which this issue was entered into JIRA.|
|Updated||The time and date on which this issue was last edited.|
|Resolved||The time and date on which this issue was resolved.|
|Estimate||The Original Estimate of the total amount of time required to resolve the issue, as estimated when the issue was created.|
|Remaining||The Remaining Estimate, i.e. the current estimate of the remaining amount of time required to resolve the issue.|
|Logged||The sum of the Time Spent from each of the individual work logs for this issue.|
|Development||If you use Bitbucket or Stash to manage your code repositories, you can create code brances in your code development tools directly from JIRA issues. See Integrating JIRA with Code Development Tools for details.|
|Agile||Let's you view your issue on your Scrum or Kanban board.|
Some of the most important fields are described as below.
JIRA can be used to track many different types of issues. The default types are listed below, but please note that your JIRA administrator may have customized this list to suit your organization.
Bug — A problem which impairs or prevents the functions of the product.
Improvement — An enhancement to an existing feature.
New Feature — A new feature of the product.
Task — A task that needs to be done.
Custom Issue — A custom issue type, as defined by your organization if required.
An issue's priority indicates its relative importance. The default priorities are listed below; note that both the priorities and their meanings can be customized by your JIRA administrator to suit your organization.
Highest — Highest priority. This problem will block progress.
High — Indicates that this issue is causing a problem and requires urgent attention.
Medium — Indicates that this issue has a significant impact.
Low — Indicates that this issue has a relatively minor impact.
Lowest — Lowest priority.
Each issue has a status, which indicates where the issue currently is in its lifecycle ('workflow'). An issue starts as being 'Open', then generally progresses to 'Resolved' and then 'Closed'; or, depending on circumstances, it may progress to other statuses. Please also note that your JIRA administrator may have customized the available statuses to suit your organization.
Open — This issue is in the initial 'Open' state, ready for the assignee to start work on it.
In Progress — This issue is being actively worked on at the moment by the assignee.
Resolved — A Resolution has been identified or implemented, and this issue is awaiting verification by the reporter. From here, issues are either 'Reopened' or are 'Closed'.
Reopened — This issue was once 'Resolved' or 'Closed', but is now being re-examined. (For example, an issue with a Resolution of 'Cannot Reproduce' is Reopened when more information becomes available and the issue becomes reproducible). From here, issues are either marked In Progress, Resolved or Closed.
Closed — This issue is complete.
An issue can be resolved in many ways, only one of them being 'Fixed'. A resolution is usually set when the status is changed. The default resolutions are listed below; note that your JIRA administrator may have customized these to suit your organization.
Fixed — A fix for this issue has been implemented.
Won't Fix — This issue will not be fixed, e.g. it may no longer be relevant.
Duplicate — This issue is a duplicate of an existing issue. Note: it is recommended you create a link to the duplicated issue.
Incomplete — There is not enough information to work on this issue.
Cannot Reproduce — This issue could not be reproduced at this time, or not enough information was available to reproduce the issue. If more information becomes available, please reopen the issue.
Won't Do — This issue won't be actioned. (This resolution is the same as Won't Fix, and is only available for software projects by default)
Note that once an issue has been resolved (that is, the issue's Resolution field is not empty), textual references to that issue will show the key in strikethrough text.