Jira Tutorial PDF
Jira Tutorial PDF
This tutorial will guide the users on how to utilize this tool to track and report bugs in different
applications.
Audience
This tutorial has been prepared for professionals who want to learn the uses of the JIRA tool.
It will provide the readers enough understanding on the various components of JIRA with
suitable examples.
Prerequisites
As a reader of this tutorial, you should be aware of the contents that have to be provided in
a bug. Additionally, it will help if you have knowledge of the bug and testing lifecycle as well.
Copyright &Disclaimer
Copyright 2018 by Tutorials Point (I) Pvt. Ltd.
All the content and graphics published in this e-book are the property of Tutorials Point (I)
Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish
any contents or a part of contents of this e-book in any manner without written consent of
the publisher.
We strive to update the contents of our website and tutorials as timely and as precisely as
possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt.
Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website
or its contents including this tutorial. If you discover any errors on our website or in this
tutorial, please notify us at [email protected]
i
JIRA
Table of Contents
About the Tutorial .......................................................................................................................................... i
Audience ........................................................................................................................................................ i
Prerequisites .................................................................................................................................................. i
1. JIRA – OVERVIEW.......................................................................................................................1
7. JIRA – LOGIN............................................................................................................................23
8. JIRA – DASHBOARD..................................................................................................................25
ii
JIRA
Configure Fields........................................................................................................................................... 40
Deleting a Link............................................................................................................................................. 74
iii
JIRA
iv
JIRA
1. JIRA – Overview
JIRA is an Incident Management Tool used for Project Management, Bug Tracking, Issue
Tracking and Workflow. JIRA is based on the following three concepts – Project, Issue and
Workflow.
JIRA supports MySQL, Oracle, PostgreSQL and SQL server in the backend.
JIRA can be integrated with many other tools – Subversion, GIT, Clearcase, Team
Foundation Software, Mercury, Concurrent Version System and many more.
JIRA is a commercial tool and available as a Trial version for a limited time.
To utilize JIRA services, a license is required.
JIRA provides free license for academic projects.
A 15-day trial version is available for an individual person to use.
Use of JIRA
Following are some of the most significant uses of JIRA.
JIRA can be used in Helpdesk, Support and Customer Services to create tickets and
track the resolution and status of the created tickets.
1
JIRA
Core
S. No. Description
Features
3 Task Details Status of every task, comment, attachment and due dates are
stored in one place.
2
JIRA
Scale with
JIRA supports any business team and any project irrespective of
7 Team
size and complexity.
Growth
Mobile App It is available on Google Play Store and App Store (iTunes) of
10
Apple.
3
JIRA
2. JIRA – Project
A Project contains issues; a JIRA project can be called as a collection of issues. A JIRA Project
can be of several types. For example –
The following screenshot shows how to reach to the Create Project button from the
Dashboard.
Choose the type of Project that suits your requirement and the process it should follow.
4
JIRA
Once the type of project is selected, click on Next. The user will see the flow of the project
based on the selection. Here, we have selected Basic Software development.
The following screenshot displays the available issue types and the workflow for the chosen
project in the step mentioned above:
5
JIRA
Click on the Select button, enter the name of the project and confirm the Key that the user
wants to display as a reference in all the issues. Once this is done, click on the Submit button.
The following screenshot displays the fields to provide details before the creation of a project.
The page having issues will display. The following screenshot displays whether any issues are
linked with a new created project.
6
JIRA
3. JIRA – Issues
JIRA is a project management tool and uses issues to track all the tasks. An issue helps to
track all works that underlie in a project. In real time, every work or task either technical,
non-technical, support or any other type of a project in JIRA are logged as an issue.
Story of a project
Task of a story
Sub-task of a story
A defect or bug can be an issue
Helpdesk Ticket can be logged as issue
Leave Request
The following screenshot shows the basic page and information of an open issue.
7
JIRA
4. JIRA – Workflow
In JIRA, workflow is used to track the lifecycle of an Issue. Workflow is a record of statuses
and transitions of an issue during its lifecycle. A status represents the stage of an issue at a
particular point. An issue can be in only one status at a given point of time like Opened, To
Do, Done, Closed, Assigned, etc.
A transition is a link between two statuses when an issue moves from one status to another.
For an issue to move between two statuses, a transition must exist. In a simple way, a
transition is some kind of work done on the issue, while status is the impact of work on that
issue.
Example
As of now, an issue is created and opened. When the assignee starts working on the issue,
the issue moves to the In Progress status. Here, the transition is starting the work, while
the status of the issue is now progressive.
JIRA workflow has the following stages to track as soon as an issue is created:
Open Issue: After creation, the issue is open and can be assigned to the assignee to
start working on it.
In Progress Issue: The assignee has actively started to work on the issue.
Resolved Issue: All sub-tasks and works of that Issue are completed. Now, the issue
is waiting to be verified by the reporter. If verification is successful, it will be closed or
re-opened, if any further changes are required.
Reopened Issue: This issue was resolved previously, but the resolution was either
incorrect or missed a few things or some modifications are required. From Reopened
stage, issues are marked either as assigned or resolved.
JIRA Workflow can be referred as a Defect Lifecycle. It follows the same concepts; the only
difference is that it is generic for all issues rather than limited to Defects only.
7
JIRA
A transition is a one-way link, if an issue moves back and forth between two statuses; two
transitions should be created.
Example: There are two-way transitions between closed and re-opened statuses. A closed
issue can be reopened if any modifications are required at any time until the project
completes, while a re-opened issue can be closed directly if additional work is taken care in
another issue and no specific work has been done on the re-opened issue.
8
JIRA
5. JIRA – Installation
JIRA is a pure Java based application and supports all OS platforms like Windows,
Linux of different versions or MAC, etc., those satisfy JDK/JRE requirements.
JIRA supports all famous browsers like Chrome, IE, Mozilla and Safari.
System Requirements
Since JIRA is a web-application, it follows the concept of client/server. It means that JIRA can
be installed centrally on a server and users can interact with it through web-browsers using
a website from any computer.
Browser: JavaScript should be enabled, the user is recommended not to use any
script-blocking tool like NoScript to access full functionality of JIRA.
JDK/JRE: It is recommended to update JRE/JDK with the latest version. JIRA 6.4
recommends using JRE/JDK version 8.
Since our scope is to consume the JIRA application as end users, we can ignore the server
side requirements.
At the server side, JIRA must connect with relation database to store issues/application
data.
Download the JIRA Windows Installer.exe file from the following link –
https://www.atlassian.com/software/jira/download?_ga=1.28526460.1787473978.1
488778536
9
JIRA
The following screenshot shows how to download the .exe file for a specific OS.
Run the .exe file to run the installation wizard. The following screenshot shows the
downloaded .exe file.
10
JIRA
After clicking the .exe file, the Run confirmation pop-up displays, click on RUN. The following
screenshot shows the RUN confirmation pop-up.
11
JIRA
Choose the appropriate installation option as shown in following screenshot and then click on
Next.
The installation summary is displayed with the Destination Directory, Home Directory, TCP
Ports, etc., as shown in the following screenshot.
12
JIRA
Click on Install. JIRA will start installing as displayed in following screenshot. It takes a couple
of minutes to finish the installation.
After installation, JIRA will be started automatically if the check box to “Start JIRA Software
7.3.4 now” is checked. Then click on Next, if not, it can be accessed using the appropriate
Windows Start Menu shortcut.
13
JIRA
14