www.atlassian.com Open in urlscan Pro
13.227.213.13  Public Scan

Form analysis
1 forms found in the DOM

GET #

<form action="#" method="GET"> <label for="footer-language-selector" aria-label="Choose language"></label> <select id="footer-language-selector" option="language-selector" name="url" style="width: 3.6rem">
    <option disabled="">Choose language</option>
    <option aria-label="Deutsch" class="notranslate SL_opaque" data-lang="de" data-width="4rem" value="https://www.atlassian.com/de/software/jira/guides/issues/overview">Deutsch</option>
    <option selected="" aria-label="English" class="notranslate SL_opaque" data-lang="en" data-width="3.6rem" value="https://www.atlassian.com/software/jira/guides/issues/overview">English</option>
    <option aria-label="Español" class="notranslate SL_opaque" data-lang="es" data-width="4rem" value="https://www.atlassian.com/es/software/jira/guides/issues/overview">Español</option>
    <option aria-label="Français" class="notranslate SL_opaque" data-lang="fr" data-width="4.1rem" value="https://www.atlassian.com/fr/software/jira/guides/issues/overview">Français</option>
    <option aria-label="Italiano" class="notranslate SL_opaque" data-lang="it" data-width="3.8rem" value="https://www.atlassian.com/it/software/jira/guides/issues/overview">Italiano</option>
    <option aria-label="한국어" class="notranslate SL_opaque" data-lang="ko" data-width="2.9rem" value="https://www.atlassian.com/ko/software/jira/guides/issues/overview">한국어</option>
    <option aria-label="Nederlands" class="notranslate SL_opaque" data-lang="nl" data-width="5.4rem" value="https://www.atlassian.com/nl/software/jira/guides/issues/overview">Nederlands</option>
    <option aria-label="日本語" class="notranslate SL_opaque" data-lang="ja" data-width="3.15rem" value="https://www.atlassian.com/ja/software/jira/guides/issues/overview">日本語</option>
    <option aria-label="Polski" class="notranslate SL_opaque" data-lang="pl" data-width="3.1rem" value="https://www.atlassian.com/pl/software/jira/guides/issues/overview">Polski</option>
    <option aria-label="Português" class="notranslate SL_opaque" data-lang="br" data-width="4.85rem" value="https://www.atlassian.com/br/software/jira/guides/issues/overview">Português</option>
    <option aria-label="русский" class="notranslate SL_opaque" data-lang="ru" data-width="4.1rem" value="https://www.atlassian.com/ru/software/jira/guides/issues/overview">русский</option>
    <option aria-label="中文" class="notranslate SL_opaque" data-lang="zh" data-width="2.35rem" value="https://www.atlassian.com/zh/software/jira/guides/issues/overview">中文</option>
  </select>
  <script type="text/x-component"> { "type":"imkt.components.LanguageSelector", "params": { } } </script>
</form>

Text Content

Close
View this page in Deutsch?
All languages
Choose your language
 * 中文
 * Deutsch
 * English
 * Español
 * Français
 * Italiano
 * 한국어
 * Nederlands
 * 日本語
 * Português
 * Pусский
 * Polski

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

 * Get it free
 * 
 * Features
 * Product guide
 * Templates
 * Pricing
 * Enterprise
 * 
 * More +
 * Less -

 * 
 * Get it free
 * 
 * Sign in
 * 

Back



--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

Get it free



Getting started
Introduction to Jira
Jira for Teams
7 Steps to Get Started in Jira
Projects
Overview
Tutorials
Resources
Boards
Overview
Tutorials
Resources
Issues
Overview
What is an issue?What are issue types?What is Jira issue hierarchy?What is the
anatomy of an issue?What are parent and child issues?What are linked issues?
Tutorials
Resources
Workflows
Overview
Tutorials
Resources
Integrations
Overview
Tutorials
Resources
Reports and Dashboards
Overview
Tutorials
Resources
Insights
Overview
Tutorials
Resources
Permissions
Overview
Tutorials
Resources
JQL
Overview
Tutorials
Cheat sheet
Resources
Automation
Overview
Tutorials
Resources
Timeline
Overview
Tutorials
Resources
Advanced planning
Overview
Tutorials
Resources
Mobile Apps
Overview
Tutorials
Resources
More about Jira
Editions of Jira
Hosting options


JIRA ISSUES OVERVIEW


WHAT IS AN ISSUE?

In Jira, teams use issues to track bugs and individual pieces of work that must
be completed. Depending on how your team uses Jira, an issue could represent a
project task, a helpdesk ticket, a leave request form, etc. In Jira, issues
typically represent individual work items such as big features, user
requirements, and software bugs. You can update issues to show work progress or
add relevant information such as who is assigned to the work, in-depth
description, or attachments.


Watch full demo

--------------------------------------------------------------------------------


WHAT ARE ISSUE TYPES?

Jira has different issue types that can help you identify, categorize, and
distinguish between different types of work. The issue types out-of-the-box
include:

EPIC

Represents a larger body of work. Epics are often represented as a collection of
multiple issues.
Example: Start a lemonade stand.

TASK

Represents a task that needs to be done. Tasks are used as ‘catch-alls’ and when
the work cannot be accurately represented by the other issue types.
Example(s): Make lemonade. Create sign. Set-up stand.

STORY

Represents a requirement expressed from the perspective of the user.
Example: As a lemonade enthusiast, I’d like to have a really cold, crisp drink.

BUG

Represents a problem that needs to be fixed.
Example: The lemonade is too sour.

SUB-TASK

Represents a more granular decomposition of the work required to complete a
standard issue. A sub-task can be created for all issue types.
Example: Squeeze lemons.

Sub-tasks are child issues that can be added after an issue has been created.

--------------------------------------------------------------------------------


WHAT IS JIRA ISSUE HIERARCHY?

Let’s think about hierarchy in the context of an organization. At the top, you
have your CEO. This person is supported by group of executives, who are also
supported by a wider group of employees. Similarly, Jira’s issue hierarchy
levels showcases how pieces of work ladder up to broader initiatives and
represent different levels of detail in a plan’s scope. Jira's built-in issue
hierarchy from top to bottom is as follows:

 1. Epics - Epics represent broad objectives or large bodies of work that can be
    broken down into stories, tasks, and bugs.
 2. Issues (task, story, bug) - Stories and tasks are issues that represent work
    that needs to be completed in support of those larger goals. Bugs are
    problems that impede the progress or functionality of work.
 3. Sub-tasks - A granular piece of work required to complete a story, task, or
    bug.



Each Jira product comes with these default issue types, but Jira admins can
create and customize issue types to match any method of project management that
suits your team! Learn more

There are additional levels of hierarchy above epic available in the Premium
edition of Jira. Compare plans

--------------------------------------------------------------------------------


WHAT IS THE ANATOMY OF AN ISSUE?

Issues capture a lot of information about a piece of work, such as assignee, due
date, status, and more. In Jira, we refer to each of these elements as an issue
field. You can create a custom field to collect information that isn’t available
in the default system fields. Learn more

Choosing which fields appear on your team's issues, which of those fields are
most important, and where those fields appear can help your team move work
forward faster. The issue view's design enables great flexibility in where you
place your fields. An issue’s layout can be separated into 5 key regions:


 1. Description: Since this section is the first place users look when they open
    an issue, your most important fields should be configured here.
 2. Field tabs: If the issue layout's screen is configured with more than one
    tab, they'll show up here. Field tabs can be leveraged to organize
    information that may be relevant to different teams, for example.
 3. Context fields: Fields above the hide when empty line in configuration
    appear here in the Details group. Each user can pin their most important
    context fields into the Pinned fields group depending on what works for
    them.
 4. More fields: Fields under hide when empty are placed in this group when they
    don't have a value. When they have a value, they'll appear in the Details
    group.
 5. Configure issue layout: Click Configure to change the position and
    visibility of fields in the issue view.

--------------------------------------------------------------------------------


WHAT ARE PARENT AND CHILD ISSUES?

Parent and child are terms that describe a type of relationship between issues:

 * A parent issue is an issue that sits above another issue e.g. a task is made
   up of sub-tasks
 * A child issue is an issue that sits below another issue e.g. a sub-task that
   belongs to a task

This means that the parent and child relationship isn’t limited to specific
issue types. Rather, any issue type can be both a parent and a child issue — the
only exception being subtasks, which can only be a child since there aren’t any
issue types below it in the hierarchy.



--------------------------------------------------------------------------------


WHAT ARE LINKED ISSUES?

As with any project, there may be dependencies between your tasks. You can
easily represent this association in Jira by linking issues together.
Associations that come out-of-the-box are:

 * blocks/is blocked by
 * clones/is cloned by
 * duplicates/is duplicated by
 * relates to



All linked issues will appear on each issue. This makes it easier for teams to
navigate between connected work and showcase dependencies.

Company
Careers
Events
Blogs
Investor Relations
Atlassian Foundation
Contact us

PRODUCTS

Rovo
Jira
Jira Align
Jira Service Management
Confluence
Trello
Bitbucket
See all products

RESOURCES

Technical support
Purchasing & licensing
Atlassian Community
Knowledge base
Marketplace
My account
Create support ticket

LEARN

Partners
Training & certification
Documentation
Developer resources
Enterprise services
See all resources

Copyright © 2024 Atlassian

Privacy Policy
Terms
Impressum
Choose language Deutsch English Español Français Italiano 한국어 Nederlands 日本語
Polski Português русский 中文
This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Manage
preferences. Otherwise, clicking Accept all cookies indicates you agree to our
use of cookies on your device. Clicking Reject all cookies means you do not
agree to our use of non-strictly necessary cookies on your device.Atlassian
Cookies and Tracking Notice
Manage preferences Reject all cookies Accept all cookies



MANAGE PREFERENCES

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Accept all

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They are based on uniquely identifying your
browser and internet device. If you do not allow these cookies, you will
experience less targeted advertising.

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. If you do not
allow these cookies we will not know when you have visited our site, and will
not be able to monitor its performance.

Back Button


COOKIE LIST



Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Reject all Confirm my choices