JIRA Tutorial

JIRA is a project management tool used for issues and bugs tracking system. It is widely used as an
issue-tracking tool for all types of testing. This tutorial introduces the readers to the fundamental
features, usage, and advantages of JIRA. This tutorial will guide the users on how to utilize this tool
to track and report bugs in different applications.

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.

Important Points to Note

The following points explain some interesting details of JIRA.
 JIRA is an incident management tool.
 JIRA is developed by Atlassian Inc., an Australian Company.
 JIRA is a platform independent tool; it can be used with any OS.
 JIRA is multi-lingual tool − English, French, German, Japanese, Spanish, etc.
 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.
License and Free Trial
The following points describes the legalities of the JIRA Tool.
 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 is used in Bugs, Issues and Change Request Tracking.
 JIRA can be used in Help desk, Support and Customer Services to create
tickets and track the resolution and status of the created tickets.
 JIRA is useful in Project Management, Task Tracking and Requirement
Management.
 JIRA is very useful in Workflow and Process management.
JIRA - Core Features
The following table explains some of the most important and commonly used features in
detail for better understanding.

Sr.No Core Features & Description

 Boards
JIRA supports Scrum and Kanban boards.
1 These boards provide an immediate snapshot of the project to the team.
Helps to quickly review the progress of the project and see the status of the individual tasks.
Board workflow can be customized to fulfil the way a team wants to proceed.

Business Project Template

JIRA supports n number of business templates to manage simple tasks and complex tasks l
workflow.
2
Template can be customized based on the team and their approach. Ex: Workflow can be customiz
based on each team's approach.
Every step is accounted and team can move to achieve their goals.

Task Details
3 Tasks can be defined at the individual level to track the progress.
Status of every task, comment, attachment and due dates are stored in one place.

Notifications
An email can be sent for a particular task to the users.
4 Voting and watching features to keep an eye on the progress for the stakeholders.
Use @mention to get the attention of a specific team member at Comments/Description.
User will instantly notify if something is assigned or if any feedback is required.

Power Search
JIRA supports a powerful search functionality with Basic, Quick and Advanced features.
5
Use the search tool to find answers like due date, when a task was last updated, what items a tea
member still needs to finish.
Project information at one place, search within a project.

6
Reports
JIRA supports more than a dozen reports to track progress over a specific timeframe, deadlin
individual’s contribution, etc.
 Easy to understand and generate different reports those help to analyze how the team is going on.
Easy to configure these reports and display the matrices to the stakeholders.

Scale with Team Growth

7
JIRA supports any business team and any project irrespective of size and complexity.

Add -Ins
8 JIRA supports more than 100 add-ins to connect with different software to make work easy.
Wide range of add-ins makes it as universal across the globe.

Multilingual
9
JIRA supports more than 10 languages those are widely used as English (US, UK, India), Frenc
German, Portuguese, Spanish, Korean, Japanese and Russian.

Mobile App
JIRA is available as a Mobile Application as well.
10
It is available on Google Play Store and App Store (iTunes) of Apple.
Easy to stay connected with the team while moving anywhere with notification, comments a
project activity.

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 −

 Software Development Project

 Marketing Project
 Migration to other platform project
 Help Desk Tracking Project
 Leave Request Management System
 Employee Performance System
 Website Enhancement
Create a New Project
To create a project, the user should login as a JIRA Service Desk Admin and then Click on
Project → Create Project.
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.
The following screenshot displays the type of projects available in 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 −
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.
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.
 Close Issue − The issue is considered as finished, resolution is correct as of
now. Closed issues can be re-opened later based on the requirement.
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.
The following diagram shows a standard workflow −
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.
In this chapter, we will learn how to install JIRA on your system.

Important Points to Note

 JIRA is a web application that provides a private website to an individual or a
set of requested users belonging to the same company/project.
 JIRA can be run as a Windows Service at the server side.
 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.
 It supports Mobile browsers as well in mobile views.
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.

Installation at the Server Side

 JIRA follows the Client/Server concept. At the server side, JIRA must be
installed before using it as end user.
 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.
 Select the OS type and click on Download.
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.
After clicking the .exe file, the Run confirmation pop-up displays, click on RUN. The
following screenshot shows the RUN confirmation pop-up.

The following JIRA installation wizard displays, click on Next.

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.
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.
Click the Finish button.

The installer will create the following shortcuts on the start menu −

 Access JIRA
 Start JIRA Server
  Stop JIRA server
 Uninstall JIRA
The following screenshot shows the above-mentioned shortcuts −

Select the license type and enter organization name as shown in following screenshot −
Click on Generate License

A confirmation pop-up will display as shown in the following screenshot. Click on Yes.
Set up the administration account as displayed in the following screenshot.

JIRA will automatically finish the setting-up as shown below −

Once JIRA finishes the setup and starts running in the server, the user can access it from a
browser on any computer with network access to the JIRA server.

Previous Page Print PageNext Page

To create an issue in JIRA, the user should have Create Issue permission in the project.
Admin can add/remove the permission.

Steps to Follow
Click on the Create button in the navigation bar to open the create issue dialogue box.
To complete the process of creating an issue, we should follow the pointers given below.
 Select the Project where the issue is.
 Select the type of issue, whether it is a bug/new feature/story, etc.
 Write a one-line summary to provide the overall idea about the issue.
 Write the details of the issue in the Description field. Explain the issue, so that
stockholders can understand every detail of the issue.
 To create a similar type of issue in the same project and issue type, check the
checkbox of “Create another” otherwise keep it as unchecked.
 After entering all the details, click on the Create button.
The following screenshot shows how to create an issue by providing the required and
optional details.
If the “Create another” checkbox is not checked, after clicking on the Create button, the user
will have to navigate to the Dashboard and a pop-up will display on the right side with
an issue id and summary.
The following screenshot shows how to know whether the issue is successfully created or
not.

If the “Create another” checkbox is checked while clicking on the Create button, the user will
get a new create issue page along with the issue id.
The following screenshot shows the page, if the user has checked the “Create another” box.
Configure Fields
To add other fields in the Create Issue form, click on “Configure fields” at the top right hand
side of the page. The following screenshot shows how to configure the fields in the Create
Issue page.

After clicking on the Configure fields button, a drop down box will be displayed, click on
Custom. The following screenshot shows the available fields under the Custom tab.

By checking and unchecking the checkboxes to show and hide, fields will be added or cleared
from the form. The following screenshot shows the available fields under the All tab.
Now navigate to Create Issue, all fields based on choices will be displayed in the form that
shows up. The following screenshot shows the configured fields in the Create Issue page.

The fields in the Create Issue form are explained below.

 Priority − Issue creator can set the priority to resolve the issue as High,
Medium, Low, and Lowest.
 Labels − It is similar to Tag; it helps in filtering out specific types of issues.
 Linked Issue − It links other issues that are either dependent on this issue or
this issue is dependent on them. Options in dropdowns are – block, is blocked
by, duplicate, clone, etc.
 Issue − User can link the issue by the Typing ID or summary of those that are
related to the linked issue field.
 Assignee − The person who is responsible to fix this issue. Assignee name can
be entered by the issue creator.
  Epic Link − An Issue creator can provide an epic link, if the issue belongs to
any of those.
 Sprint − The user can define in which sprint, this issue belongs to, when this
issue should be addressed.
In the next chapter, we will learn how to clone an issue.
Cloning means to copy. To clone an issue means to create a duplicate issue within the same
project. A cloned issue can be treated as a new issue and edited like other issues.
We should consider the following points while cloning an issue.
 A cloned issue is completely a separate issue from the original issue.
 Any action or operation taken on the original issue does not have any impact
on the clone issue and vice-versa.
 The only connection between the original and clone is the link that is created.
 Information that is carried from the original issue to clone issue is as follows −
o Summary
o Description
o Assignee
o Environment
o Priority
o Issue Type
o Security
o Component
o Reporter
o Affects Version
o Fix Version
o Attachment
o Projects
o Content of custom fields are also cloned
 Information that is not cloned −
o Time Tracking
o Comments
o Issue History
o Links to confluence pages

Steps to Follow for Cloning

Open a JIRA issue that is supposed to be cloned. Select More → Clone when the screen
appears. The following screenshot shows how to access the Clone functionality.
In the clone screen, there are a few options given to the users, which are as follows −
 A user can change the summary while cloning it.
 If the issue contains links to other issues, a user can check the checkbox to
contain the clone issue or uncheck if the user does not want to be a part of the
clone issue.
 If the issue has sub-tasks, the user can select/deselect the checkbox to contain
the sub-tasks in clone or not.
 The same is applicable for attachment as well.
 It also gives an option, whether to carry or not – the sprint value to the new
clone issue.
The following screenshot shows how to clone an issue by providing the necessary details.
The next step is to click on Create. It will display the clone issue details. If the user does not
change the clone words while creating, it can be visible in the summary, links and sub-tasks.
The following screenshot shows how a cloned issue is displayed.

JIRA has powerful and very efficient search functionalities. A user can search issues across
Projects, Versions and Components using various search types. JIRA allows saving the
search criteria to utilize next time as filters; even these filters can be shared by others as well.

Types of Searching Options

JIRA has a couple of fundamental ways to search issues. The most important ones are as
follows.

 Basic Search
 Quick Search
Let us now understand both of these search types in detail.

Basic Search
Basic Search in JIRA is a user-friendly interface that can be used easily to find out the issues.
It uses the JQL queries in the backend. To do a basic search in JIRA, the user has to follow
the steps given below.
Step 1 − Navigate to issues → Search Issues. The following screenshot shows how to access
the Search for Issues feature −
Step 2 − A search page displays. If it has any existing Search criteria, then click on the New
Filter to reset it. The following screenshot shows how to define a new search criteria.

Step 3 − Set the search criteria against different fields like Project, Type, Status and
Assigned. Then click on More and select any field to search with additional fields. The
following screenshot shows what all criteria’s can be set to search issues.
Step 4 − If the user wants to search against any specific text, keywords, start typing in
the Contains text box. The following screenshot shows how to search specific text in issues.

Step 5 − A user can use wildcards or operators in all text based fields to search specific
strings. For example −

 Single character wildcard - te?t

 Multiple characters wildcard – win*
 Boolean operators - "atlassian jira" || confluence
Based on different search criteria, the following result is displayed. The following screenshot
shows the list of searched issues.
How to Save a Search
To save the searched criteria, the user should follow the steps given below.
Step 1 − Click on Save As at the top of the page. The following screenshot shows how to
save the search criteria for future use.

Step 2 − Type the filter name and click on Submit. The following screenshot shows how to
provide a name of new search criteria before saving.
Step 3 − A Filter will appear on the left side of the Search Page under the Favourite filters
and it will have a few options like – Rename, Delete, Copy and Remove from Favourites.
The following screenshot shows the saved search criteria and the available actions to
perform.

Quick Search
The quick search is the fastest way to define search criteria. It is a text box where the user
enters the key, text or anything and it starts searching for the exact matches in the current
project and provides the result.
The Quick Search box is available on the top right hand corner of the navigator. The
following screenshot shows how to access the Quick Search feature.
Smart Querying
The quick search option performs smart searches with minimal typing. It recognizes the
following word and gives out several options to the user to choose.
 my − This word searches issues assigned to the logged-in user.
The following screenshot shows different smart querying in a quick search.

Some of the most commonly used smart querying options are as follows −
 r:me − Finds issues reported by the logged-in user.
 r:abc − Finds issues reported by user – abc.
 r:none − Finds issues with no reporter.
 <project name> or <project key> − Finds issues within the given project
name or finds issues having the same project key.
  Overdue − Finds issues those are overdue before today.
 Created:, updated:, due: − These smart searches finds issues with Created,
Updated, or Due Date using the prefixes created:, updated:, or due:,
respectively. For the date range, use today, tomorrow, yesterday, a single date
range (e.g. '-1w'), or two date ranges (e.g. '-1w,1w'). Date ranges cannot have
spaces between them. Valid date/time abbreviations are: 'w' (week), 'd' (day),
'h' (hour), 'm' (minute).

part from the type of searches explained in the previous chapter, JIRA also has a few
advanced search options, which can be performed using the following three ways.

 Using Field Reference

 Using Keyword Reference
 Using Operators Reference
These above-mentioned three ways have been explained in detail below.
The user should consider the following points while performing any advanced search.
 Advanced search uses structured queries to search for JIRA issues.
 Search results displays in the Issue Navigator.
 Search results can be exported to MS Excel and many other available formats.
 Save and Subscribe features are available to advanced searches.
 An advanced search uses the JIRA Query Language known as JQL.
 A simple query in JQL consists of a field, operator, followed by one or more
values or functions. For example, the following simple query will find all
issues in the "WFT" project −
Project = "WFT"
 JQL supports SQL like syntax such as ORDER BY, GROUP BY, ISNULL()
functions, but JQL is not a Database Query Language.
Using Field Reference
A field reference means a word that represents the field name in the JIRA issue including the
custom fields. The syntax is −
<field name> <operators like =,>, <> “values” or “functions”
The operator compares the value of the field with value presents at right side such that only
true results are retrieved by query.

 Go to Issues → Search for Issues in the navigator bar.

The following screenshot shows how to navigate the Search section.
If there is an existing search criterion, click on the New Filter button to reset the criteria. The
following screenshot shows how to start with a new criteria −

Type the query using the Field, Operator and Values like issueKey = “WFT-107”.
There are other fields as well – Affected Version, Assignee, Attachments, Category,
Comment, Component, Created, Creator, Description, Due, Environment, etc. As soon as the
user starts typing, the auto-complete functionality helps to write in the defined format.
The following screenshot shows how to add Field Name criteria using advanced features.
Operator selection − The following screenshot shows how to select operators.

The next step is to enter the value and then click on the Search symbol. The following
screenshot shows how to add values and search.
The following screenshot shows the search result based on criteria set.

Using Keyword Reference

Here, we will understand how to use a keyword reference and what its advantages are
A keyword in JQL −

 joins two or more queries together to form a complex JQL query.

 alters the logic of one or more queries.
 alters the logic of operators.
 has an explicit definition in a JQL query.
 performs a specific function that defines the results of a JQL query.
List of Keywords −

 AND − ex - status = open AND priority = urgent And assignee = Ashish.

 OR − ex – duedate < now() or duedate is empty.
 NOT − ex – not assignee = Ashish .
 EMPTY − ex - affectedVersion is empty / affectedVersion = empty.
 NULL − ex – assignee is null.
 ORDER BY − ex – duedate = empty order by created, priority desc.
Similar to field reference, as soon as the user starts typing, the auto-complete functionality
helps to get the correct syntax. The following screenshot shows how to add keywords.

Click on the Search symbol and it will provide the search results. The following screenshot
shows the result based on a criteria set.
Using Operators Reference
Operators are used to compare values of the left side with the right side, such that only true
results display as the search result.
List of Operators
 Equals: =
 Not Equals: !=
 Greater Than: >
 Less Than: <
 Greater Than Equals: =>
 Less than equals: =<
 IN
 NOT IN
 CONTAINS: ~
 Does Not contain: ! ~
 IS
 IS NOT
 WAS
 WAS IN
 WAS NOT IN
 WAS NOT
 CHANGED
Similar to the Field and the Keyword Reference, these operators can also be used to enhance
the search results.
IRA provides different types of reports within a project. It helps to analyze the Progress,
Issues, Showstoppers and Timeliness of any Project. It also helps to analyze the resource
utilization as well.

How to Access Reports

To access reports in JIRA, the user should go to Project → choose Specific project. The
following screenshot shows how to navigate to a specific project.
Click on the Reports icon on the left side of the page. It will display all the reports supported
by JIRA. The following screenshot shows how to access the Report section.

When the user clicks on Switch report, it will display the list of reports. The following
screenshot shows list of reports available for quick switch.
Type of Reports
JIRA has categorized reports in four levels, which are −

 Agile
 Issue Analysis
 Forecast & Management
 Others
Let us now discuss the features of the above-mentioned report categories in detail.
Agile
Following are the list of features of Agile Reports.
 Burn down Chart − Track the total work remaining, also whether sprint is
achieving the project goal or not.
 Sprint Chart − Track the work completed or pushed back to the backlog in
each sprint.
 Velocity Chart − Track the amount of work completed from sprint to sprint.
 Cumulative Flow Diagram − Shows the statuses of issues over time. It helps
to identify high-risk issues or unresolved important issues.
 Version Report − Track the projected release date for a version.
 Epic Report − Shows the progress towards completing an epic over a given
time.
 Control Chart − Shows the cycle time for the product, its version or the
sprint. It helps to identify whether data from the current process can be used to
determine future performance.
 Epic Burn Down − Track the projected number of sprints required to
complete the epic.
 Release Burn Down − Track the projected release date for a version. It helps
to monitor whether the version will release on time, so mandatory action can
be taken if work is falling behind.
Issue Analysis
Following are the list of features of Issue Analysis.
 Average Age Report − Displays the average age in days of unresolved issues.
 Created Vs Resolved Issue Report − Display the number of issues created vs
the number of issues resolved in given period.
 Pie chart Report − Shows a pie chart of issues for a project grouped by a
specified field.
 Recently Created Issue Report − Shows the number of issues created over a
time-period for a project and how many of those were resolved.
 Resolution Time Report − Displays the average time taken to resolve issues.
 Single Level Group by Report − .It helps to group the search results by a
field and see the overall status of each group.
 Time since Issues Report − It helps to track how many issues were created,
updated, resolved, etc., over a time-period.
Forecast & Management
Following are the list of features of Forecast and Management type of reports.
 Time Tracking Report − Shows the original and current time estimates for
issues in the current project. It can help to determine whether work is on track
for those issues.
 User Workload Report − Shows the time estimates for all unresolved issues
assigned to a user across projects. It helps to understand how much a user is
occupied, whether overburdened or has less work.
 Version Workload Report − Displays how much outstanding work is
remaining per user and per issue. It helps to understand the remaining work of
a version.
In addition to these, there are other types of reports that generally have a pie chart in them,
which we
A workload pie chart displays a pie chart showing all the issues for a specific project. Let us
understand how to use it in JIRA.

Generate a Report
To generate a report, the user should follow the steps given below.
Step 1 − Go to Project → choose the Specific project. Click on the Report icon on the left
side of the menu. Go to ‘Others’ section and click on Workload Pie Chart Report as shown in
the following screenshot.
Step 2 − Select Project or issue filter for which to generate the report. In the Statistic Type,
select the field name on which the pie chart will be formed. Select the Time Field to report on
as Current Estimate, Original Estimate or Time Spent.
The following screenshot shows how to generate a report by providing details.

Step 3 − Click on Next to generate the report. The following screenshot shows how the
generated report looks like.
It displays the number of created issues versus resolved issues over a given time-period. It
helps to understand whether the overall backlog is moving towards resolution or not.

Generate a Report
To generate a report, the user should follow the steps given below.
Step 1 − Go to Project → choose a specific project. Click on the Report icon on the left side
of the menu. Go to Issue Analysis and click on Created Vs Resolved Issues Report. The
following screenshot shows how to access the Created Vs Resolved issues report −

Step 2 − Select the Project or the issue filter for which the report has to be generated. Select
the time-period to see reports like Daily, Weekly, Monthly, Quarterly, Annually, etc.,
available in the dropdown box. Enter the number of days in the Days Previously field to
show in the graph. Select Yes or No for Cumulative totals. Select Display Versions as All
Versions from the dropdown list.
The following screenshot shows how to generate report by selecting different available fields.

Step 3 − Click on Next to generate the reports. The following screenshot shows how the
generated report looks like.

The created issues are displayed in red, while the resolved issues are in green color.
It displays the total work remaining to achieve the sprint goal for a given time to sprint. It
helps the team to manage the progress and respond accordingly. This chart is an important
feature of Agile – Scrum methodology.
Generate a Report
To generate a report, the user should follow the steps given below.
Step 1 − Go to Project → choose a Specific project. Click on the Report icon on the left side
of the menu. Go to Agile and click on Burndown chart. The following screenshot shows how
to access a Burndown Chart.

Step 2 − It displays the Burndown chart of the sprint like how the team is progressing
towards a committed task. The red line displays how much work is remaining, while the grey
line shows the committed tasks. The team can see where they stand in terms of the progress
of sprint as compared to the commitment at the starting of that sprint. The user can change
the Sprint and Y-axis by selection from a dropdown.
The following screenshot shows how the Burndown chart looks like sprint wise.
Step 3 − In the second part of the report, it displays data like what is the sprint start date,
what all issues were added, day by day how many issues resolved, what story points of the
issues are, and day-by-day how many story points are remaining. This data is utilized to
create the chart. The following screenshot shows the data that is used to generate the chart.

Note − Quite similar to these reports, other reports can also be generated.