Issue fields and statuses

Configuring issues

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

These are the pieces that make up the issues you work on: 

Issue fields

Expand to view issue fields
FieldDescription
Project
The parent project to which the issue belongs.
KeyA 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.)
SummaryA brief one-line summary of the issue. For example, "Red Angry Nerd is scary."
TypeSee below for a list of types.
StatusThe stage the issue is currently at in its lifecycle (workflow). See below for a list of statuses.
PriorityThe importance of the issue in relation to other issues. (See below for a list of priorities).
ResolutionA record of the issue's resolution, if the issue has been resolved or closed. (See below for a list of resolutions).

Affects Version(s)
(if applicable)

Project version(s) for which the issue is (or was) manifesting.
Fix Version(s)
(if applicable)		Project version(s) in which the issue was (or will be) fixed.
Component(s)
(if applicable)		Project component(s) to which this issue relates.
Labels
(if applicable)		Labels to which this issue relates.
Environment
(if applicable)		The hardware or software environment to which the issue relates.
DescriptionA detailed description of the issue.
LinksA list of links to related issues. (Strikethrough text, like this, indicates that an issue has been resolved.)
AssigneeThe person to whom the issue is currently assigned. Note that you cannot assign issues to a user group.
ReporterThe person who entered the issue into the system.
VotesThe number shown indicates how many votes this issue has.
Watchersnumber shown indicates how many people are watching this issue.
Due
(if applicable)		The date by which this issue is scheduled to be completed.
CreatedThe time and date on which this issue was entered into Jira.
UpdatedThe time and date on which this issue was last edited.
ResolvedThe time and date on which this issue was resolved.
EstimateThe Original Estimate of the total amount of time required to resolve the issue, as estimated when the issue was created.
RemainingThe Remaining Estimate, i.e. the current estimate of the remaining amount of time required to resolve the issue.
LoggedThe sum of the Time Spent from each of the individual work logs for this issue.
Development *If you use Bitbucket to manage your code repositories, you can create code branches in your code development tools directly from Jira issues. See Integrating with development tools for details.
Agile *Lets you view your issue on your Scrum or Kanban board.
Service Desk **Lets you view request participants and view the equivalent request in the customer portal

* Only available in Jira Software

projects, and only available to Jira Software users

** Only available in Jira Service Management projects, and only available to Jira Service Management users

Issue types

Your default issue types depend on what Jira application you have installed. We've listed all the default issue types for each application:

Expand to view Jira Core issue types
TypeDescription
TaskA task represents work that needs to be done.
Sub-taskA sub-task is a piece of work that is required for a task.
Expand to view Jira Software issue types
TypeDescription
TaskA task represents work that needs to be done.
Sub-taskA sub-task is a piece of work that is required for a task.
StoryA user story is the smallest unit of work that needs to be done.
BugA bug is a problem which impairs or prevents the functions of a product.
EpicA big user story that needs to be broken down.
Expand to view Jira Service Management issue types
TypeDescription
IT HelpRequesting help for IT related problems.
PurchaseRequesting hardware or software.
ChangeRequesting a change in current IT profile.
FaultReporting a fault.
AccessRequesting additonal access.

Issue priorities

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 administrator to suit your organization.

Expand to view issue priorities
PriorityDescription
HighestHighest priority. Indicates that this issue takes precedence over all others.
HighIndicates that this issue is causing a problem and requires urgent attention.
MediumIndicates that this issue has a significant impact.
LowIndicates that this issue has a relatively minor impact.
LowestLowest priority.

Issue resolutions

An issue can be completed, or resolved, in many ways. An issue resolution is usually set when the status is changed. The default resolutions are listed below; note that your administrator may have customized these to suit your organization.

Expand to view Jira Core issue resolutions
ResolutionDescription
DoneThe work is completed.
Won't doThe work will not be done.
DuplicateThis work is being tracked elsewhere.
Expand to view Jira Software issue resolutions
ResolutionDescription
DoneThe work is completed.
Won't doThe work will not be done.
DuplicateThis work is being tracked elsewhere.
Cannot reproduceThe issue cannot be reproduced.
Expand to view Jira Service Management issue resolutions
ResolutionDescription
DoneThe work is completed.
Won't doThe work will not be done.
DuplicateThis work is being tracked elsewhere.

Note that once an issue has been resolved (that is, the issue's Resolution field is filled in), textual references to that issue will show the key in strikethrough text. 

Last modified on Nov 16, 2022

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.