Bugzilla Interview Questions and Answers

1) What is Bugzilla?
Bugzilla is a Web based Defect Management Tool allows Testing and Development teams to post and
track defects and it is an Open source tool.
2) What is the deployment environment for Bugzilla
Bugzilla developed in LAMP (Linux, Apache, MySQL and PHP) technology.
3) What is the difference between Quality Center and Bugzilla?
Quality Center is a Test Management Tool, supports Complete Application Life Cycle Management;
Requirements Management,
Test Design,
Test Execution,
Defect Management,
Traceability etc
Bugzilla supports Defects Management only
Note: Defect Management is part of Test Management.
4) What are the advantages of Bugzilla?
Bugzilla can increase the productivity and accountability of individual employees by providing a
documented workflow and positive feedback for good performance.

5) How to create User Account in Bugzilla?

a. Enter "E-mail address" and "Real Name" in the spaces provided, then select the "Create Account"
button.
b. Within moments, you should receive an email to the address you provided above, which contains your
login name (generally the same as the email address), and a password that you can use to access your
account.

6) What is The Bugzilla Query Page?

The Bugzilla Query Page is the heart and soul of the Bugzilla user experience. It is the master interface
where we can find any bug report, comment, or patch currently in the Bugzilla system.
7) How to Write a Bug Report in Bugzilla?
Bug report is ones that get bugs fixed. A bug report normally has two qualities:
Producible and Reproducible
8) What about Account Settings page?
On this page, we can change our basic Account Settings, including our password and full name; for
security reasons.
9) What about Watching Users functionality?
By entering user email names into the "Users to watch" text entry box, delineated by commas, we can
watch bugs of other users. This powerful functionality enables seamless transitions as developers change
projects, managers wish to get in touch with the issues faced by their direct reports, or users go on
vacation.
10) What about Email Settings page?
Here we can reduce or increase the amount of email sent us from Bugzilla.
11) What are Bugzilla features?
The Bugzilla features are as follows:
Integrated, product-based granular security schema
Inter-bug dependencies and dependency graphing
Advanced reporting capabilities
A robust, stable RDBMS back-end
Extensive configurability
a very well-understood and well-thought-out natural bug resolution protocol
Email, XML, console, and HTTP APIs
Etc
12) What are Bugzilla Components?

Bugzilla component include:

Administration of Bugzilla:
Bugzilla-General
The Bugzilla documentation
Email, Anything to do with email sent by Bugzilla
Query/Buglist, Anything to do with searching for bugs and viewing the buglists.
Reporting/Charting, and Generating Reports
User Accounts, Anything about managing a user account from the user's perspective.
User Interface, General issues having to do with the user interface cosmetics (not functionality)
including cosmetic issues, HTML templates, etc.
13) How to change user name in Bugzilla?
We can't. However, the administrative account can, by simply opening user account in editusers.cgi and
changing the login name.
14) Does Bugzilla allow the user to track multiple projects?
Yes, We can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as
many "Components" as we want.
15) If I am on many projects, and search for all bugs assigned to me, will Bugzilla list them for me
and allow me to sort by project, severity etc?
Yes
16) Does Bugzilla allow attachments (text, screenshots, urls etc)?
Yes.
17) Does Bugzilla allow us to define our own priorities and levels?
Yes. However, modifying some fields, notably those related to bug progression states, also require
adjusting the program logic to compensate for the change.
18) Can email notification be set up to send to multiple people, some on the To List, CC List, BCC
List etc?
Yes
19) If there is email notification, do users have to have any particular type of email application?

Bugzilla email is sent in plain text, the most compatible mail format on the planet.
20) Does Bugzilla allow data to be imported and exported
Bugzilla allows data export through a custom DTD in XML format. It does not, however, export to
specific formats other than the XML Mozilla DTD.
21) Can a user create and save reports?
Yes user can create and save reports.
22) Can users save reports in Word format? Excel format?
No
23) Can a user modify an existing report and then save it into another name?
We can save an unlimited number of queries in Bugzilla. We are free to modify them and rename them.
24) Can the admin person establish separate group and individual user privileges?
Yes
25) Are there any backup features provided?
MySQL, the back-end for Bugzilla, allows backup of data.
26) Are there any security problems with Bugzilla?
The Bugzilla code has not undergone a complete security audit. It is recommended that you closely
examine permissions on your Bugzilla installation, and follow the recommended security guidelines.
27) How do I set up the email interface to submit/change bugs via email?
You can find an updated README.mailif file in the contrib/ directory of your Bugzilla distribution that
walks you through the setup
28) I want to manually edit some entries in my database. How?
There is no facility in Bugzilla itself to do this.

29) What is Red Hat Bugzilla?

Bugzilla is a bug tracking system developed at mozilla.org. It was originally used to track the bugs in the
Mozilla web browser. Red Hat has customized it to track bugs in their Linux products.
30) When Bugzilla was launched?
In 1998
31) What is the latest version of Bugzilla?
Bugzilla 4.2
32) What are the System Requirements to deploy Bugzilla?
Bugzilla's system requirements include:

A compatible database management system (MySQL)

A suitable release of Perl 5
An assortment of Perl modules
A compatible web server (Apache)
A suitable mail transfer agent, or any SMTP server

32) What does Bugzilla do?

Track bugs and code changes
Communicate with teammates
Submit and review patches
Manage quality assurance (QA)

Introduction- What is Bugzilla

Bugzilla is an open-source issue/bug tracking system that allows developers effectively to keep track of
outstanding problems with their product. It is written in Perl and uses MYSQL database.
Bugzilla is a defect tracking tool, however it can be used as a test management tool as such it can be
easily linked with other test case management tools like Quality Center, Testlink etc.
This open bug-tracker enables users to stay connected with their clients or employees, to communicate
about problems effectively throughout the data-management chain.
Key features of Bugzilla includes

Advanced search capabilities

E-mail Notifications
Modify/file Bugs by e-mail
Time tracking
Strong security
Customization
Localization

In this tutorial, we will learn about

Log-in to Bugzila account

Creating a BugReport
Create graphical reports
How to use Browse Function
How to send mail to assignee
How to use Simple Search Option in Bugzilla
How to add or remove column to default search screen
How to use Advance Search Option in Bugzilla
How to use Preferences in Bugzilla

How to log-in to Bugzilla

Step 1) To create an account in Bugzilla or to login into the existing account go to New Account or Log
inoption in the main menu.

Step 2) Now, enter your personal details to log into Bugzilla

1.

User ID

2.

Password

3.

And then click on "Log in"

Step 3) You are successfully logged into Bugzilla system

Creating a Bug-report in Bugzilla

Step 1) To create a new bug in Bugzilla, visit the home-page of Bugzilla and click on NEW tab from the
main menu

Step 2) In the next window

1.

Enter Product

2.

Enter Component

3.

Give Component description

4.

Select version,

5.

Select severity

6.

Select Hardware

7.

Select OS

8.

Enter Summary

9.

Enter Description

10.

Attach Attachment

11.

Submit

NOTE: The above fields will vary as per your customization of Bugzilla

NOTE: The mandatory fields are marked with *.

In our case field's

Summary
Description

Are mandatory
If you do not fill them you will get a screen like below

Step 4) Bug is created ID# 26320 is assigned to our Bug. You can also add additional information to the
assigned bug like URL, keywords, whiteboard, tags, etc. This extra-information is helpful to give more
detail about the Bug you have created.
1.

Large text box

2.

URL

3.

Whiteboard

4.

Keywords

5.

Tags

6.

Depends on

7.

Blocks

8.

Attachments

Step 5) In the same window if you scroll down further. You can select deadline date and also status of the
bug.Deadline in Bugzilla usually gives the time-limit to resolve the bug in given time frame.

Create Graphical Reports

Graphical reports are one way to view the current state of the bug database. You can run reports either
through an HTML table or graphical line/pie/bar-chart-based one. The idea behind graphical report in
Bugzilla is to define a set of bugs using the standard search interface and then choosing some aspect of
that set to plot on the horizontal and vertical axes. You can also get a 3-dimensional report by choosing
the option of "Multiple Pages".
Reports are helpful in many ways, for instance if you want to know which component has the largest
number of bad bugs reported against it. In order to represent that in the graph, you can select severity on

X-axis and component on Y-axis, and then click on generate report. It will generate a report with crucial
information.

The graph below shows the Bar chart representation for the Bugs severity in component "Widget
Gears". In the graph below, the most severe bug or blockers in components are 88 while bugs with
normal severity is at top with 667 number.

Likewise, we will also see the line graph for %complete Vs Deadline

Step 1) To view your report in a graphical presentation,

Click on Report from Main Menu

Click on the Graphical reports from the given option

Step 2) Let's create a graph of % Complete Vs Deadline

In here on the vertical axis we chose % Complete and on our horizontal axis we chose Deadline. This
will give the graph of amount of work done in percentage against the set-deadline.
Now, set various option to present reports graphically
1.

Vertical Axis

2.

Horizontal Axis

3.

Multiple Images

4.

Format- Line graph, Bar chart or Pie chart

5.

Plot data set

6.

Classify your bug

7.

Classify your product

8.

Classify your component

9.

Classify bug status

10.

Select resolution

11.

Click on generate report

The image of the graph will appear somewhat like this

Browse Function

Step 1) To locate your bug we use browse function, click on Browse button from the main menu.

Step 2) As soon as you click on browse button a window will open saying "Select a product category to
browse" as shown below, we browse the bug according to the category.

After clicking the browse button

Select the product "Sam's Widget" as such you have created a bug inside it

Step 3) It opens another window, in this click on component "widget gears". Bugzilla Components are
sub-sections of a product. For instance, here our product is SAM'S WIDGET whose component
is WIDGET GEARS.

Step 4) when you click on the component, it will open another window. All the Bugs created under
particular category will be listed over-here. From that Bug-list, choose your Bug#ID to see more details
about the bug.

It will open another window, where information about your bug can be seen more in detail. In the same
window, you can also change the assignee, QA contact or CC list.

How to use Simple search option in BugZilla

Bugzilla provides two ways of searching bugs, they are Simple Search and Advance Search methods.

Step 1) We will first learn the "Simple Search" method. Click on search button from the main menu and
then follow these steps
1.
2.

Click on "Simple Search" button

Choose the status of the Bug choose Open if you are looking the bug in Open status and closed
for bug in closed status

3.

Choose your category and component, and you can also put keywords related to your bug

4.

Click on the search

Step 2) Here we will search for both option open and closed status, first we have selected closed status
for bug and clicked search button.

For closed status, it fetched 12 bugs.

Step 3) Likewise we have searched for Open status as well, and it has fetched 37 bugs related to our
queries.

Also, at the bottom of the screen you have various options like how you want to see your bug - an XML
format, in Long format or just Time summary. Apart from that you can also use other option like send
mail to bug assignee, change several bugs at once or change column of the screen, etc.

In next step, we will demonstrate one of this function change column of the screen, through which we
will learn how to add or remove the column to the existing column.

How to add or remove column to default search screen

Step 1) Click on the Change Column as shown in above screen-shot. It will open a new window where
you have to follow these steps.

Select any given option from the column you want to appear in the main screen - here we have
selected % complete
Click on the arrow button, it will move % complete column from Available Column to
the Selected column
These steps will move the selected column from left to right.

The % complete is moved from left to right as shown below, and once we click on change column it will
appear in the main screen

Before- Search result screen before using "Change Column" option

There is no % complete column appears in search screen result as shown below

After- Search result screen after using "Change Column" option

You can see % complete column added to the extreme right in the existing column in the main
screen, which was not their previously.

NOTE: Likewise you can remove or add any column you want.

How to use Advance Search in BugZilla

Step 1) After Simple search we will look into Advanced Search option for that you have to follow the
following steps.

1.

Click on advanced search option

2.

Select option for summary, how you want to search

3.

Enter the keyword for your bug- for example, Widget gears twisted

4.

Select the category of your Bug under classification, here we selected Widget

5.

Choose your product under which your Bug was created- Sam's Widget

6.

Component- Widget gears

7.

Status- Confirmed

8.

Resolution

Step 2) Once you select all the option, click on search button. It will detect the bug you created

The advance search will find your bug, and it will appear on the screen like this

How to use preferences in BugZilla

Preferences in Bugzilla is used to customize the default setting made by Bugzilla as per our requirement.
There are mainly five preferences available

General Preferences
E-mail Preferences
Saved Searches
Account Information
Permissions

General Preferences

For general preferences, you have various option like changing Bugzilla general appearance, position
of the additional comment box, automatically add me to cc, etc. Here we will see how to change the
general appearance of the Bugzilla.
There are many changes you can do which are self-explanatory, and you can choose the option as per
your requirement.
Step 1)

To set the background Skin of Bugzilla

Go to Bugzilla general preference (Skin)
Select the option you want to see as a change and submit the change ( DuskClassic )
A message will appear on the window saying changes have been saved, as soon as you submit the
changes

After the skin preference is changed to Classic from Dusk, the back-ground color of the screen appears
white

Likewise, for other default settings changes can be done.

E-mail preferences
E-mail preferences enable you to decide how to receive the message and from whom to receive the
messages.
Step 1) To set the e-mail preferences

1.

Click on e-mail services

2.

Enable or disable the mail to avoid receiving notification about changes to a bug

3.

Receiving mail when someone asks to set a flag or when someone sets a flag you asked for

4.

When and from whom you want to receive mail and under which condition. After marking your
option at the end, submit the changes.

Saved Searches Preference

Saved searches preference gives you the freedom to decide whether to share your bug or not to share.

Step 1) Click on saved searches, it will open window with the option like editbugs, don't share,
canconfirm, etc. Choose the option as per your need.

Step 2) We can run our bug from "Saved Searches".

Go to Saved Searches under preference

Click on the "Run" button

As soon as you run your search from Saved Searches it opens your bug as shown below

Step 3) In the same window we can also choose specific users with whom we want to share the search by
marking or unmarking the checkbox against the users

That's all to BugZilla!

JIRA Tutorial: A Complete Guide for Beginners

JIRA is a tool developed by Australian Company Atlassian. It is used for bug tracking, issue
tracking, and project management. The name "JIRA" is actually inherited from the Japanese word
"Gojira" which means "Godzilla".
The basic use of this tool is to track issues, and bugs related to your software and mobile apps. It is also
used for project management. The JIRA dashboard consists of many useful functions and features which
make handling of issues easy. Some of the key features are listed below.

Topics covered in this Tutorial

1- JIRA Scheme
2- JIRA Issues and Issue types

2.1- What is JIRA Issue?

2.2- Issue Types

3- JIRA Components
4- JIRA screen
5- Issue Attributes
6- Issue Security Schemes

6.1- System Administration

7- How to create an issue in JIRA

7.1- Sub-Task
7.2- WorkFlows
7.3- Plug-ins in JIRA
7.4- JIRA Agile
7.5- Creating issue in Agile
7.6- How to create an Epic in Agile
7.7- Use of Clone and Link in JIRA

8- Reports in JIRA

8.1- Kanban Board and Managing issues

8.2- JIRA Scrum Vs JIRA Kanban

JIRA Scheme
Inside JIRA scheme, everything can be configured, and it consists of

Workflows
Issue Types
Custom Fields
Screens
Field Configuration
Notification
Permissions

JIRA Issues and Issue types

What is JIRA Issue?

JIRA issue would track bug or issue that underlies the project. Once you have imported project then you
can create issues.
Under Issues, you will find other useful features like

Issue Types
Workflow's
Screens
Fields
Issue Attributes

Let see JIRA Issue in detail

Issue Types
Issue Type displays all types of items that can be created and tracked via JIRA. JIRA Issues are classified
under various forms like new feature, sub-task, bug, etc. as shown in the screen shot.

There are two types of Issue types schemes in JIRA, one is

Default Issue Type Scheme: In default issue type scheme all newly created issues will be added
automatically to this scheme
Agile Scrum Issue Type Scheme: Issues and project associated with Agile Scrum will use this
scheme

Apart from these two issue type schemes, you can also add schemes manually as per requirement, for
example we have created IT & Support scheme, for these we will drag and drop the issue types from
the Available Issue type to Issue type for current scheme as shown in the screen shot below

JIRA Components

Components are sub-sections of a project; they are used to group issues within a project into smaller
parts. Components add some structures to the projects, breaking it up into features, teams, modules,
subprojects and more. Using components you can generate reports, collect statistics, and display it on
dashboards and so on.
To add new components, as shown in the above screen you can add name, description, component lead
and default assignee.

JIRA screen
When issue is created in JIRA, it will be arranged and represented into different fields, this display of
field in JIRA is known as a screen. This field can be transitioned and edited through workflow. For each
issue, you can assign the screen type as shown in the screen-shot. To add or associate an issue operation
with a screen you have to go in main menu and click on Issues then click on Screen Schemes and then
click on "Associate an issue operation with a screen" and add the screen according to the requirement.

Issue Attributes
Issue Attributes encompasses

Statuses
Resolutions
Priorities

Statuses: Different statuses are used to indicate the progress of a project like To do, InProgress, Open,
Closed, ReOpened, and Resolved. Likewise, you have resolutions and priorities, in resolution it again
tells about the progress of issue like Fixed, Won't fix, Duplicate, Incomplete, Cannot reproduce,
Done also you can set the priorities of the issue whether an issue is critical, major, minor, blocker and
Trivial.

Issue Security Schemes

This function in JIRA allows you to control who can view the issues. It consists of a number of security
levels which can have users or groups assigned to them. You can specify the level of security for the
issues while creating or editing an issue.
Similarly, there is a Default Permission Scheme any new project that are created will be assigned to this
scheme. Permission Schemes allow you to create a set of permissions and apply this set of permission to
any project.
System Administration
Some of the useful features that JIRA admin provides to users are:

Audit Log
Under Audit Log, you can view all the details about the issue created, and the changes made in the
issues.

Issue Linking
This will show whether your issues link with any other issue that is already present or created in the
project also you can de-activate Issue linking from the panel itself

Mail in JIRA
Using Mail system in admin you can mail issues to an account on a POP or IMAP mail server or
messages written to the file system generated by an external mail service.

Events
An event describes the status, the default template and the notification scheme and workflow transition
post function associations for the event. The events are classified in two a System event (JIRA defined
events) and Custom event (User defined events).

Watch list
JIRA allows you to watch a particular issue, which tells you about the notifications of any updates
relating to that issue. To watch an issue, click on the word "watch" in the issue window, and if you
want to see who is watching your issues, you have to click on the number in brackets.

Issue Collectors
In the form of JIRA issues, an issue collector allows you to gather feedback on any website. In
administration if you click on Issue collectors an option will open asking Add Issue Collector. Once
you have configured the look and feel of an Issue Collector, embed the generated JavaScript in any
website for feedback.

Development Tools
You can also connect your development tools to JIRA using this admin function. You have to enter the
URL of the application to connect with JIRA.

How to create an issue in JIRA

JIRA Dashboard will open when you enter your user ID and password. Under JIRA dashboard you will
find option Project, when you click on it, it will open a window that list out options like Simple Issue
Tracking, Project Management, Agile Kanban, Jira Classic and so on as shown in screen shot below.

When you click on option Simple Issue Tracking, another window will open, where you can mention all
the details about the issue and also assign the issue to the responsible person.

When you click on "Submit" button, a window will open where you can perform a list of work like
creating issues, assigning issues, check the status of issues like- resolved, In-Progress or closed and so on.

Once the issue is created a pop-up will appear on your screen saying your issue is created successfully as
shown in the screen shot below

Now if you want to edit an issue or you want to export the issue to XML or Word document, then you can
hover your mouse on main panel and click on Issues. Under Issues options click on search for issues that
will open a window from where you can locate your issues and perform multiple functions.

When you select the "search for Issues" under Issues, a window will appear as shown in the screen shot

1.

Search for issues option will bring you to a window where you can see the issues created by you
like here we have issues ST1 and ST2

2.

3.
4.

5.

Here in the screen shot you can see the issue "Bug detected while User Acceptance Testing" and
all the details related to it. From here, you can perform multiple tasks like you can stop the progress on
issues, edit the issues, comment on the issues, assigning issues and so on
Even you can export issue details to a XML or Word document.
Also, you can view activity going on the issue, reviews on the issue, work log, history of the issue
and so on.
Under the time tracking option, you can even see the estimation time to resolve the issues

In the same window, you can set a filter for the issue and save them under Favorite Filters, so when you
want to search or view a particular issue you can locate it using the filter.
To view the summary of the issue, you can click on options summary, this will open a window which will
show all the details of your project and progress on this chart. On the right-hand side of the summary
window, there is an Activity Stream which gives the details about the issues and comments made by the
assignee on the issue.

Sub-Task

Subtask issues are useful for splitting up a parent issue into a number of smaller tasks that can be assigned
and tracked separately. It addresses issues more comprehensively and segregates the task into smaller
chunks of task to do.
How to create Sub-Task
Sub-Task can be created in two ways

Create sub-task under parent issue

Creating an issue into a sub-task

To create sub-task in JIRA, you have to select an issue in which you want to assign the sub-task. Under
the issue window, click on Assign more option, and then click on create sub-task as shown in the
screenshot below. You can also select convert to sub-task under same tab to convert the parent issue into a
sub-task.

Once you click on Create Sub-Task, a window will pop up to add sub-task issue. Fill up the details about
the sub-task and click on Create as shown in below screen-shot, and this will create sub-task for the
parent issue.

It will create a sub-task under parent issues, and details will appear about when to complete the task on
the issue type page as shown in the screenshot below. If you would like to add more sub-task, you can
click on the plus (+) sign on the corner of the sub-task panel. Likewise, if you want to note down the time
spent on the present task, click on (+) plus sign in the corner of the time tracking and put down the details
in the log sheet.

Some important points to remember while creating Sub-Task

You can have as many sub-task as needed under an Issue

You cannot have a sub-task for a sub-task
Once a sub-task is created under a parent, parent cannot be converted into a sub-task

A sub-task can however be converted into a parent issue

You can work on your sub-task without having navigating away from the parent issue

WorkFlows
A JIRA workflow is a set of statuses and transitions that an issue goes through during its lifecycle. JIRA
workflow encompasses five main stages once the issue is created.

Open Issue
Resolved Issue
InProgress Issue
ReOpened Issue
Close Issue

While workflow in JIRA comprises of Statuses, assignee, resolution, conditions, validators, postfunction's and properties

Statuses: It represents the positions of the issues within a workflow

Transitions: Transitions are the bridges between statuses, the way a particular issue moves from
one status to another
Assignee: The assignee dictates the responsible party for any given issue and determines how the
task would be executed

Resolution: It explains why an issue transitions from an open status to a closed one
Conditions: Conditions control who can perform a transition
Validators: It can ensure that the transition can happen given the state of the issue
Properties: JIRA recognizes some properties on transitions

You can assign the status of the issue from the window itself, when you click on the check box for IN
Progressstatus as shown in screen shot below, it will reflect the status in the issue panel highlighted in
yellow.

For the issue that we have created, JIRA will present a workflow which maps the progress of the project.
As shown in screenshot whatever status that we have set in the Issue panel it will be reflected in
Workflow chart, here we have set the issue status in "In Progress" and same status is updated in the
workflow, highlighted in yellow. Workflow can give a quick overview of the work under process.

Plug-ins in JIRA
There are plug-ins available for JIRA to work more effectively, some of these plugins are Zendesk,
Salesforce, GitHub, Gitbucket and so on. Some of them enables support team to report issues directly into
JIRA, creates unlimited private repositories with full featured issue and project management support, etc.
JIRA Agile
Agile or Scrum method is generally used by development teams who follows a roadmap of planned
features for upcoming versions of their product. Agile follows the same roadmaps to track their issues as
in other JIRA methods To do -> In Progress -> Done , as shown in the screen shot below, we have one
issue in To do and the second issue in In Progress. Once the issue in In Progress will be resolved, it will
move to Done status and in the same way the issue in To do will move to the next stage In Progress.

Creating issue in Agile

To create agile issue, go to main menu under Agile tab, click on "Getting Started", when you click on it, it
will ask to create new board for the issues for Scrum or Kanban. You can choose your option as per your
requirement, here we have selected Scrum method.

How to create an Epic in Agile

In JIRA Agile, an epic is simply an issue type. The epic captures a large body of work. It is a large user
story which can be broken down into a number of small stories. To complete an epic, it may take several
sprints. You can either create a new epic in agile or either use the issue you have created in normal JIRA
board. Likewise, you can also create a story for agile scrum.

Plan Mode in Agile:

Plan mode displays all the user stories created for the project. You can use the left-hand side menu to
decide the basis on which the issues need to be displayed. While on the right-hand side menu clicking on
the issue, you can create subtasks, logwork, etc.
Work Mode in Agile
It will display the active sprint information. All the issues or users stories will be displayed into three
categories as shown in the screen shot below To do, In Progress and Done to show the progress of the
project or issues.
Use of Clone and Link in JIRA
In JIRA, you can also clone the issue, one advantage of cloning an issue is that the different team can
work separately on the issue and resolve the issue quickly.

There is another useful function is JIRA Link, Issue linking allows you to create an association between
two existing issues on either the same or different JIRA servers. As shown in the screen shot, we have
linked the current issue "ST-6 Drop down menu is not working" with another issue " ST-4 GUI is not
responsive- retest GUI functions".

Like here we have set sprint for 1 day and it will run sprint for that specific time period as shown in the
screenshot below. If you are working with scrum, and want to prioritize the issue or rank the issue then
you just have to simply drag and drop the issue into the backlog.
Apart from this there are multiple task that you can do, for instance if you click on the right side corner of
the window a list of function will pop up which you can use it as per your need.

Reports in JIRA
To track the progress in Agile, a Burndown Chart shows the actual and estimated amount of work to
be done in the sprint. A typical burndown chart will look somewhat like this, where the red line
indicates the actual task remaining while the blue line indicates ideal task remaining during the scrum
cycle.

Apart from Burn down chart there are other options available in JIRA like Sprint Report, Epic Report,
Version Report, Velocity Chart, Control Chart, Cumulative flow diagram. You can also use different chart
option to represent the progress of your project.

Like here in the screen shot above, we have selected a pie chart for issue priorities. It will generate a Pie
Chart representing the priorities and severity of the issues in percentage for the whole project as shown
below. You can view the pie chart from different perspectives like Assignee, Components, Issue Type,
Priority, Resolution, and Status and so on.

You can also configure how you want to see the scrum board. Scrum board gives various options through
which you can make changes into your board appearance. Various features you can configure using scrum
are Columns, Swimlanes, Quick Filters, Card colors and so on. Here we have selected column
management, and selected the options Issue count, and it will show the total number of issue in progress,
to do or done. In column management, we can add an additional column as per our requirement likewise
there are different features that you can configure in board.

Filters
You can also set filters other than default filters to filter the issues. The filters that you can use are date,
component, priority, resolution and so on.

Kanban Board and Managing issues

Like Agile Scrum board, we can also create a Kanban Board, here we have created a project name Cloud
Testing. Kanban board is useful for the team that managing and constraining their work in progress.
Kanban boards are visible in Work mode but not in Plan mode.

Here we have created an issue " Bug detected while load testing" and "Check issues related to cloud
server" in Kanban Board as shown in the screenshot below, it also shows their status as well highlighted
in red.

Kanban is considered as the best methodology for bug fixing and maintenance release, where incoming
task is prioritized and then worked accordingly. There are few measures which can make Kanban more
efficient.
1.

Visualize your workflow

2.

Limit the work in progress

3.

Work on Issues

4.

Measure the cycle time

JIRA Scrum vs. JIRA Kanban

Scrum

Kanban

Reports

Reports

Burndown Chart: The chart shows all the changes and scope
changed while the sprint is still on, other charts include Sprint
Report, Velocity Chart, Epic Report, etc.

Control Chart: It allows you to measure the cycle tim

issues, showing the mean time and actual time taken
complete issues

Agile Board

Constraints

It allows the team to see the progress of sprints. This is the work
mode, where you can see the board itself broken down into
different statuses.

Team can decide whether to increase or decrease the

number of issues that should be displayed in each sta

Backlog

Workflow

This is where team will plan sprints and estimate stories that will
go into each sprint

You can map columns to the statuses of your workflo

Simply by adding or removing columns the workflow
be changed when required.

Next >

Top of Form