(Administrators) Scrum master

install and configure

creating project
adding users

product owner:-
creatings epics and stories

Scrum master:-
creating the sprint
adding stories to the sprint
adding sub tasks to story

Testers Developers:-
adding subtasks
creating bugs

https://www.softwaretestinghelp.com/interview-questions/top-20-most-important-jira-
interview-questions-and-answers/
https://www.janbasktraining.com/blog/jira-interview-questions/ nice site

Explain what is JIRA?

JIRA is an issue tracking product, or a software tool developed by Atlassian,
commonly used for bug tracking, project management and issue tracking.

JIRA, defect tracking tool.

Defect management tools or say Bug tracking tools have been a part of software
testing and development cycles for years. “JIRA” is an incident management tool,
developed by Atlassian, which is commonly used for defect/issue tracking as well as
project management.

This defect tracking tool is not only used for convenience-related features like
recording, reporting but is also integrated directly with code development
environment.

JIRA is an efficient tool and has the capability to track any kind of
defects/issues. Agile projects are also supported by JIRA.

33) State the difference between Bugzilla and JIRA?

Bugzilla
JIRA
It is an Open Source
It is a commercial tool

Using Bugzilla might be little complicated for few due to grouping users and
granting permissions For some using JIRA would be more convenient than
Bugzilla

Bugzilla allows you to show/hide the whole custom field or specific values based on
the value of some other field JIRA enables conditional configuration based only
on Type fields and Project.

Bugzilla’s has a powerful advanced search option

JIRA lacks advance-level search options. JIRA has a flexible JQL language (JIRA
Query Language). It enables you to build arbitrary boolean expressions.

Unlike JIRA, Bugzilla allows users to select the initial status of a new issue.
Unlike Bugzilla, JIRA enables you to define multiple workflows which are applied
based on the issue’s Project and Type.

Bugzilla has only one link type: Blocks/depends and a Bug ID custom field
JIRA has configurable link types with user-defined semantics.

Q #1) Why is JIRA used?

Answer: Atlassian JIRA is basically an issue and project tracking tool which allows
us to track any project related work by following a proper workflow. Enlisted below
are few reasons which determine the usage of JIRA:

Able to track project progress from time to time.

JIRA use-cases include project management, feature implementation, bug tracking,
etc.
Work-flow can be easily customized as per our requirement.
Along with issue tracking, history of the work done on issues, when, what and by
whom can also be tracked.
JIRA is platform independent and can run anywhere.

Q #2) Explain JIRA workflow.

Answer: Workflow defines the series of steps or stages an issue/ bug goes through
during its lifecycle from creation to the closing of the issue.

The workflow here includes the creation of an issue, series of actions performed to
fix the issue and the last step includes the closing or say completion of the issue
after verification. This can also be understood by the below diagram:

jira-workflow

Q #3) Enlist the report types generated by JIRA.

Answer: There are multiple reports available in JIRA which are used to show the
project statistics throughout the project life cycle.

There are general reports available for analyzing issues as well as different
reports for Scrum projects and Kanban projects.

Following are the general reports generated as and when required for analyzing
issues:

Average Age Report

Created vs Resolved issue Report
Pie Chart Report
Recently created Issue Report
Resolution Time Report
Time Tracking Report
User Work load Report
Version Work load Report
Workload Pie chart Report

Following are the examples of reports generated for Scrum projects:

Sprint Report
Control chart
Burndown chart
Cumulative Flow diagram
Epic Report
Release Burndown
Velocity chart
Version Report

Following are the examples of reports generated for Kanban projects:

Control chart
Cumulative Flow diagram.
For generating reports for your project, follow the below steps;

Navigated to desired project dashboard.

Click on Reports tab from left-hand side to view different reports.
Click on Switch report to view the different report.
(Note: Click on the image for enlarged view)

switch-report

Q #4) Explain the step by step procedure of how an issue is created in JIRA.

Answer: Whenever an issue or defect is encountered while testing, it needs to be

reported so that the developers can work on it and take the necessary action to fix
it.

We will see step by step as how an issue is created in Atlassian JIRA.

1) Log in to your JIRA account by using valid credentials and get directed to the
dashboard.
2) Click on ‘Create’ button displayed and you will be navigated to a window for
creating an issue.
3) Enter all the necessary details as required to create an issue. As you can see
in the below image:

In Project field, project for which we are creating an issue is selected. In this
example: STH_Learning(STHL) is selected from the dropdown containing all the
available projects.

In Issue type field, the nature of the issue is selected from the dropdown which
contains option like Bug, Task, Improvement, Story, New Feature, etc. In this
example, ‘Bug’ is the nature of the issue.

Summary field contains the one line title of the issue which imparts the critical
information about the issue in a summarized way. The more effective the issue
headline, the more you can show the criticality of the issue. Of course, the
headline should be easily understood without any chances of misinterpretation.
The example I have taken here, however is not much critical.

The Reporter is the one who reports the issue. In most of the cases, the name of
the Project manager is selected in this field.

In Description field, the detailed description of the issue is written. As you can
see in the below example screenshot, Steps to reproduce the issue, Actual result,
Expected result are included in the description.

In Affect Version field, the current build version the project is selected in which
the issue has been encountered.

Fix version field is basically selected by the concerned developer people, who
choose the version as and when the work for the particular issue has been finished
and the issue has been fixed.

Priority field defines which issue should be considered first to be fixed. Tester
selects the priority of the issue from the dropdown based on its effect on the
application. This example issue is basically of a Medium priority.

In Attachment field, any video or screenshot related to the issue is being

uploaded.

In Environment field, operating system and browser details are mentioned on which
issue has been encountered.

create-issue-1

create-issue-2

4) After all the details have been completed, Click on ‘Create’ button displayed on
the window to create the new issue.

5) Issue id is generated which can be used in future reference for tracking the
progress of the issue.

Q #5) Explain the three color indicators and their significance.

Answer: For any particular issue in JIRA, 3 colors like Blue, Green and Orange is
used to denote the amount of time spent on any particular issue. This information
is displayed under ‘Time Tracking’ section. Each colour has its own significance
like;

Blue: This color is to denote the ‘Original Estimate’ i.e. the time estimate to be
invested in resolving the issue. This field has been labeled as ‘Estimated’.
Orange: This color determines the time left for resolving the issue. This field has
been labeled as ‘Remaining’.
Green: This color defines the actual time that has been used or say spent in
resolving the issue so far. This field has been labeled as ‘logged’.
time-tracking

Q #6) For any particular issue, what all are included under change history?

Answer: Change history section displays the activities of changing any records with
information regarding the person who has made the change as well as the time at
which the changes have been made.

The change history also displays the information about the old and new field values
in the case of the change in any field.

Basically, change history includes the following records of the changes:

Creation and deletion of a comment.

Creation and deletion of an issue link.
Deletion of a worklog.
File attachment changes
Issue field changes
The change history for any issue can be viewed in JIRA by following steps:

Open any particular issue.

Click on ‘History’ tab present in the ‘Activity’ section.
history-tab

Q #7) Mention a way with which an issue can be shared with other users in JIRA.

Answer: An issue can be shared with other users in JIRA by using the share option
available on the issue description page.

share-option

When share option for any particular issue is clicked, it contains the link to the
issue to be shared along with ‘Username or Email’ and ‘Note’ field that has to be
filled.

share-option-1

Q #8) What is the importance of labeling issue?

Answer: Labeling an issue is basically done to categorize an issue within a

particular section which in turn can be easily searched with the help of labels.

Label for a particular issue can be initially set at the time of creating the
issue, while it can edit also within the issue. Label field is displayed under the
‘Details’ section as shown below in the figure:

labeling-issue

Q #9) How is an issue linked in JIRA?

Answer: As the name itself defines, Linking means the association between the two.

In the same way, in JIRA issue is linked with any other issue in cases like:

Relate to another issue

Duplicate to another issue
Block another issue.
For displaying the details of the Linked issues, there are two fields available in
JIRA: ‘Linked issues’ and ‘Issues’.

linked-issues

Linked issue section contains the dropdown for the options to be selected as the
reason for linking the issue. As per the selected option, the suggestion of the
issues to be linked in displayed in ‘Issue’ dropdown.

linked-issues-1

Linking of issues can be done either on the same or different JIRA servers.

Q #10) What is the purpose of JIRA dashboard?

Answer: The first page which is displayed whenever we get logged in to JIRA
application is ‘Dashboard’ which is basically the default or system dashboard.

A personal dashboard can also be created and designed by adding different gadgets
and can be edited also as and when required. These gadgets are the means to display
the project progress in terms of issues, etc.

Let us understand the steps as how a personal dashboard can be created:

1) Enter valid credentials and get navigated to JIRA dashboard.

2) Click on “…” displayed on the upper right hand side and choose option ‘Create
dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the
currently viewed dashboard.

copy-dashboard

3) ‘Create Dashboard’ page is displayed.

4) Enter all mandatory information and click on ‘Create’ button.

create-dashboard

5) After creating a dashboard, you get navigated to a page where there are multiple
options to select and add gadgets to your dashboard.

add-gadgets

6) There is also an option available to choose and edit the layout of your
dashboard.

Any particular Dashboard can be edited, copied, shared, delete from the Manage
dashboard section.

Q #11) What do you mean by Scheduling an issue?

Answer: Scheduling the issue means scheduling the work of issue for a particular
‘due date’.

For this function to work, one must have ‘Schedule issue permission’ by JIRA
Administrator. In this case, a field with ‘Due Date’ is being populated.

Q #12) Explain how particular project details are listed in JIRA.

Answer: Every project has some main attributes which have to be displayed in the
project summary.

This attributes include:

Name of the project

Key
Components
Versions (if present)
Please refer below screenshot of Project ‘STH_L’ summary page as your reference.
Although not much activity has been done in this project but this image will give
you a clear idea.

activity

As you can see from the image, the middle display area of the page shows the
‘Activity’ screen containing details on the activities done on issues or project.

The right hand side section displays the basic information about the Project like
Project Lead, Key, Issue Status, etc.

The left hand side contains various options like Components, issues, Reports,
Active Sprints, etc. The related information is displayed as per the selection from
the option.

For Example: If I select the ‘Issue’ option, the below displayed screen will
appear.

issue-option

Q #13) What are issues types that are created and tracked via JIRA?

Answer: JIRA has some defined set of default issue types which are displayed under
‘Issue Type’ section.

Other issue types can be added, edited and deleted as per requirement of the
project. Some of the common issue types are Bug, Task, Sub-task, Epic, Story, etc.

Their details can also be seen under Issue type section as shown in the below
figure.

administration

As the definition of ‘Issue Type Schema’ mentioned in JIRA application,

An issue type scheme determines which issue types will be available to a set of
projects. It also allows specifying the order in which the issue types are
presented in the user interface. There are two types of issue type schema:

Default Issue type schema

Scrum Issue type schema
administration-1

Q #14) How is a sub-task created in JIRA?

Answer: Sub-task is the way of splitting up of parent issue into a number of small
tasks which are tracked and worked on separately.

The parent issue contains the information of all its sub-tasks which can be only of
the same project. A parent issue cannot be closed unless and until all its sub-
tasks are closed. A sub-task has the same fields as that of any standard issue but
their issue types are different.

Now, let us see step by step how a sub-task is created. I have created an issue in
the below example for the understanding creation of sub-task.

1) Open a parent issue by searching with an issue id or create any new issue id.
2) On the right hand side of the issue description screen, you will see “…” . Click
on it and options are displayed.
3) Click on Create Sub-task from the displayed dropdown option.

create-sub-task

4) Create sub-task window is displayed.

5) Enter all the mandatory details and click on ‘Create’ button.

create-button

6) Now the created sub task gets added to the parent issue under sub-task section
as shown below in the figure:

sub-task-section

7) There are also options available to convert an issue into a sub task as well as
sub task into an issue.

Q #15) Explain the term Cloning an issue.

Answer: Cloning an issue means copying an issue.

In this condition, a clone of the original issue is created which consist of same
information as is present for the original issue. Cloning of the issue is done so
that multiple users can work on the same issue, however, the operation done either
on the original issue or clone issue has no effect on each other.

All the information of the original issue are cloned expect few as mentioned below:

Time tracking
Comments’
Issue history
Status and Resolution
Let us see how to create a clone of an issue:

1) Open any issue by searching with an issue id or create any new issue id.
2) On the right hand side of the issue description screen, you will see “…” . Click
on it and options are displayed.
3) Click on Clone from the displayed dropdown option.

clone

4) Clone issue window is displayed.

5) If required, you can edit the summary of the issue and click on ‘Create’ button.

create-button

6) Another issue is created with ‘CLONE’ added in the summary.

Q #16) Explain Kanban board.

Answer: Kanban boards are created for the projects where the team has their prime
focus on visualizing the workflow and managing the project’s work in progress.

The most important feature of Kanban board is that it is found in work mode because
the projects do not have their work as planned.

Let us see how Kanban board is created in JIRA step by step.

1) Log In to the JIRA application using valid credentials and get navigated to the
dashboard.
2) Click on Project dropdown and select option ‘Create Project’.
3) Select ‘Kanban Software development’ and click on Next button.

kanban-software-development

4) Enter all the necessary details and click on Create button.

5) Kanban board is created as shown in below example.

Note: I have just taken a basic example of creation

example-of-creation

In the case of Kanban, the incoming task is given more priority and hence it is
considered as the best methodology for cases like bug fixing and maintenance
release.

Q #17) Mention one similarity and one difference between JIRA Scrum and JIRA
Kanban.

Answer:

Similarity: Both JIRA Scrum and Kanban is considered as the most powerful process
tool for optimization of work and the processes as both processes focus is on
continuous optimization and visualizing the workflow. In these cases, large and the
complex tasks are broken down and each individual tasks are worked on and completed
efficiently.

Difference: Scrum board is the work mode where progress of sprints and tracking of
its work is done. Here the team determines the list of issues that has become
backlog and then these issues are moved to sprints as per team plan.

In the case of Kanban board, the work in progress activities is being maintained
and their process flow is tracked. Here the team decides the increase and decrease
of the number of issues that is to be displayed in each status of the workflow.

Q #18) What are the most useful JIRA add-ons.

Answer: Some of the most useful JIRA add-ons are listed below:

Jenkins-CI
Usersnap
Slack
HipChat
GitHub
PagerDuty
Tempo Timesheets

Q #19) What comes under JIRA Schema?

Answer: JIRA Schema consists of the following:

Workflows
Issue types
Custom fields
Screens
Field configurations
Notifications
Permissions

Q #20) How is security setting helpful in JIRA?

Answer: Security setting for any issue is defined or say set either at the time of
creation of the issue or while editing the issue.

The basic reason for security setting is to restrict the user access to the issue
so that not all users are able to work on that issue. Security setting also allows
the access of the issue to the member of chosen security level.

https://www.softwaretestingmaterial.com/jira-interview-questions/

1. What is JIRA?
JIRA is an issue tracking product developed by Atlassian which allows bug tracking
and agile project management. The name “JIRA” is inherited from the word Gojira,
the Japanese word for Godzilla, which is a reference to a competitor Bugzilla.

2. Why is JIRA used?

Atlassian JIRA is an issue tracking and agile project management tool which allows
us to track any project by following a proper workflow. Following are the reasons
behind using JIRA.

JIRA is a platform independent that could run anywhere

JIRA can be run anywhere
In JIRA, a workflow can be easily customized based on our requirement
JIRA acts as an issue tracking as well as project management tool
JIRA allows us to track the progress of a project from time to time

3. What are the differences between JIRA and Bugzilla?

JIRA and Bugzilla are the two bug tracking tools that are widely being used by
several organizations for quite some time now.

JIRA
BUGZILLA
JIRA is a commercial tool
Bugzilla is an open source tool
JIRA is a user friendly tool compared to Bugzilla
Bugzilla is not so friendly tool compared to JIRA
Drag and drop issue prioritization is available in JIRA Drag and drop issue
prioritization is not available in Bugzilla
JIRA has configurable link types with user-defined semantics. JIRA also has
pluggable remote issue links, that allow to link an issue to any other entity
outside JIRA Bugzilla has only one link type: blocks/depends, plus a Bug ID
custom field
Unlike Bugzilla, JIRA allows to define multiple workflows which are applied based
on the issue's Project and Type Unlike JIRA, Bugzilla can let users select the
initial status of a new issue
Custom field types available in JIRA are too many to list, and even more custom
field types available from plugins Custom field types available in Bugzilla are
Text fields, Multi-selection, Drop-down, Date/time, Bug ID
JIRA allows conditional configuration based only on Project and Type fields
Bugzilla lets you show/hide the whole custom field or specific values based
on the value of some other field
JIRA lacks advance-level search options. JIRA has flexible JQL language (JIRA Query
Language) that allows you to build arbitrary boolean expressions Bugzilla's comes
with a powerful advanced search option

4. Can Jira be used for test case management?

Although JIRA was not designed to serve as a Test Case Management, it can be
configured to support test case management in two different ways.

You can either change native components in JIRA to meet test case management needs
or you can use one of the add-ons available in Atlassian Marketplace (Example:
Zephyr of JIRA)

Popular Test Management Tools

5. What is a workflow in JIRA?

Workflow is defined as a series of sequential tasks that need to be completed in
order to reach a certain goal.
A workflow in JIRA is defined as a series of sequential tasks (such as create/open
a bug, Work in progress, and completed/closed) involved in the life cycle of a bug
or an issue.

Create: Create an issue or bug

Work in progress: Series of actions performed to fix the issue
Closed: Completion of the issue after verification

JIRA Workflow
6. Explain working with workflows in JIRA?
A JIRA workflow is a set of statuses and transitions that an issue travels through
during its lifecycle and normally represents processes within your organization.
There are pre-defined built-in workflows that can’t be edited; however, you can
copy and utilize these workflows to create your own.

Working with Workflows in JIRA

7. What are the limitations when editing an active workflow?
Limitations apply when editing the draft for an active workflow:

It is not possible to edit the workflow name

Workflow statuses cannot be deleted
If a status has no outgoing transitions, it cannot have any outgoing transitions
added, regular or global
The step ID cannot be changed

8. What is a Workflow designer in JIRA?

The workflow designer in JIRA is a graphical tool that enables you to see the
layout of your workflow and to create and modify a workflow’s procedures and
transitions.

You can manage status and transitions: add, click and drag, or select to edit
properties to rename, or delete
You can add a global transition that permits different status in the workflow to
transition to the selected status. Select Allow all statuses to transition to this
one in the properties board for the transition.
You can change the screen that a transition uses.
You can configure advanced transition options such as conditions, triggers,
validators, and post functions.

9. How does a service desk work in JIRA?

Here is how Customers and Service desk agents work together to resolve a request in
JIRA.

Your customer submits a request to service agents through a portal or by email

Service desk agents see the request in their JIRA Service Desk line and investigate
the issue.
Your customer and other participants utilize the portal or email to discuss the
request with service desk agent, who works in JIRA Service Desk.
Your service agent completes the request and your customer is satisfied.

10. How are reports generated in JIRA?

Steps to follow to generate reports in JIRA are as follows:
Step 1: Navigate to the desired board and click Reports. You can find different
types of reports.
Step 2: Click Switch report to view a different report.
Step 3: Click on the switch report option to view a different report

11. What are the types of reports generated in JIRA?

JIRA provides different types of reports within a project which are used to show
the project statistics throughout the project life cycle. There are reports to
analyze issues as well as reports for Scrum and Kanban projects.

12. Name some reports generated by Kanban projects in JIRA.

The reports generated by any Kanban project in JIRA are

Control chart
Cumulative Flow diagram
13. Name some reports generated by Scrum projects in JIRA.
The reports generated by any Scrum project in JIRA are

Sprint Report
Control chart
Burn down chart
Cumulative Flow diagram
Epic Report
Release Burndown
Velocity chart
Version Report

14. Name some reports generated in JIRA for the issues tracking and analysis.

Following are the general reports generated as and when required for analyzing
issues:
Average Age Report
Created vs Resolved issue Report
Pie Chart Report
Recently created Issue Report
Resolution Time Report
Time Tracking Report
User Work load Report
Version Work load Report
Workload Pie chart Report
15. What is an issue in JIRA?
Different organizations use JIRA to track various types of issues, which can
represent anything from a software bug, to a project task, or a leave request form.

Issues are the building blocks of any JIRA project. An issue could represent a
story, a bug, a task, or another issue type in your project.

16. Explain how an issue is created in JIRA.

Let’s see step by step how an issue is created in Atlassian JIRA.
Click Create at the top of the screen to open the Create Issue dialog box.
Select the relevant Project and Issue Type in the Create Issue dialog box.
Type a Summary for the issue and complete any appropriate fields (required fields
are marked by an asterisk)
Note: Make sure you check they’re all correct before creating the next issue.
When you are satisfied with the content of your issue, click the Create button.

17. What are the color indicators in JIRA and mention their significance?
There are three color (Blue, Orange & Green) indicators in JIRA. Issue tracking
becomes easy with different color representation. These three colors are used to
denote the amount of time spent on any particular issue.

Blue Color: Blue color denotes Original Estimate i.e., the estimated time to
resolve an issue
Orange Color: Orange color denotes Remaining Estimate i.e., the remaining time to
resolve an issue
Green Color: Green color denotes Time spent or Logged i.e., the total time spent to
resolve the issue

18. What elements are included under the change history for any particular issue?
Change history for any particular issue includes the following

Creation and deletion of a comment

Creation and deletion of an issue link
Deletion of worklog
Attachment of a file
Issue field changes
19. How to view change history for any issue in JIRA?
The change history for any issue can be viewed in JIRA by following steps:

Open any issue.

Click on ‘History’ tab present in the ‘Activity’ section.
20. How an issue can be shared in JIRA with other users?
There is a share option available on the issue description page in JIRA. An issue
can be shared with other users using this share option. Once a share option is
clicked, it will ask you to provide “Username or Email” and “Note”

21. Why an issue is labeled in JIRA?

Labeling an issue in JIRA allows you to find which category an issue belongs to.
Issues can be easily searched with the help of labels. Labels can be initially set
at the time of creating the issue. It can also be modified if required.

22. How is an issue linked in JIRA?

Linking means establishing the relationship between the two. In JIRA, an issue can
be linked with other issues on either the same or different JIRA servers.

An issue can be linked with other issues as follows

An issue may relate to another issue
An issue may duplicate another issue
An issue may block another issue
23. What is the use of Move Issue wizard in JIRA?
Move Issue wizard enables you to specify another project in your JIRA instance. The
Move Issue wizard permits you to change certain attributes of the issue such as
Issue Type, Issue Status, and Custom Fields.

Issue Type: If your issue is a custom issue type that does not exist in your target
project, you must choose a new issue type.
Issue Status: If you have assigned a custom status to your issue, and it does not
exist in your target project, you must select a new issue status for your issue.
Custom Fields: If you have defined required custom fields for your issue that does
not exist in your target project, you must set values for them.

24. How to schedule an issue in JIRA?

To schedule an issue, populate its Due date field. This can be done either when
creating an issue, or at a later stage by editing the issue. Only users with the
schedule issues permission can populate the Due date field.

25. How project details are listed in JIRA?

All the projects have some attributes that are displayed under the project summary
section.
The list of attributes in JIRA is

Nature of the project

Keys for the project
Components
Version

26. What are the issues types in JIRA?

Each Jira application comes with default issue types. You can use these default
issue types or create your own to suit the needs of your projects and teams.
Here’s an example of specific issue types within each Jira application:

Jira Core default issue types:

Task – Task that needs to be done

Subtask – Smaller task within a larger piece of work
Jira Software default issue types

Story – Functionality request expressed from the perspective of the user

Bug – Problem that impairs product or service functionality
Epic – Large piece of work that encompasses many issues
Jira Service Desk default issue types

Incident – System outage or incident

Service request – General request from a user for a product or service
Change – Rollout of new technologies or solutions
Problem – Track underlying causes of incidents

27. What is Cloning an Issue in JIRA?

Cloning, or copying, an issue lets you quickly create a duplicate of an issue
within the same project. The clone issue is a replica of the original issue,
containing the same information stored in the original issue — e.g. Summary,
Affects Versions, Components, and so on. The clone issue can likewise be connected
to the original issue.

A clone issue is a different entity from the original issue. Tasks of the original
issue has no impact on the cloned issue and vice versa.

A clone issue retains the following information:

Summary
Description
Assignee
Environment
Priority
Issue Type
Security
Reporter
(If you do not have the Modify Reporter permission, the clone issue will be created
with you as the Reporter.)
Components
Affects Versions
Fix For Versions
Issue Links (optional)
Attachments (optional)
Project
(Once the clone has been saved, you can move it to another project as described in
Moving an Issue.)
The content of custom fields is also cloned.

28. What are the things that are not cloned from the original issue?
Things that aren’t cloned:

Time tracking
Comments
Issue History
Links to Confluence pages

29. How to create a clone of an issue?

Follow the steps mentioned below to create a clone of an issue

Open any JIRA issue which you wish to clone

Select More > Clone. The Clone Issue screen will appear
– You can edit the clone issue’s Summary if you wish.
– If the issue contains links to other issue(s), you can select whether or not to
include the links in the new clone issue.
– If the issue contains sub-tasks, you can select whether or not to create the sub-
tasks in the new clone issue.
– If the issue contains attachments, you can select whether or not to include the
attachments in the new clone issue.
Click Create.

30. What is a Sub-task in JIRA?

Sub-task is the way of splitting up a parent issue into a number of smaller tasks
that can be assigned and tracked separately. All the sub-tasks to a parent issue
are summarised on the parent issue’s main screen. Sub-tasks always belong to the
same project as their parent issue.

31. How is a sub-task created in JIRA?

Navigate to the issue you would like to be the parent issue of the sub-task you are
about to create.
Select More > Create Sub-Task. You will see the Create Subtask screen.
Fill in the details as needed, and then click Create at the bottom of the page.
32. How to create Kanban board in JIRA?
Let’s see step by step process of creating Kanban board in JIRA

Log In to the JIRA application using valid credentials and get navigated to the
dashboard.
Click on Project dropdown and select Create Project.
Select Kanban Software development and click Next.
Enter all the necessary details and click Create.

33. Mention some of the popular JIRA add-ons?

Some of the popular JIRA add-ons are as follows

Zephyr for JIRA – Test Management

Jenkins – CI
GitHub
Slack
Atlassian REST API Browser
ScriptRunner for JIRA
JIRA Toolkit Plugin
Tempo Timesheets

34. How to define a component in JIRA?

Components are sub-sections of a project. They are utilized to assemble issues
within a project into smaller parts.
Managing a project’s components

Sign in to JIRA as a project administrator.

Choose Settings > Projects > and click the name of a project. The Project Summary
page will appears.
Choose Components in the left menu. The Components page is shown, demonstrating a
rundown of Components and every Component’s information.
35. How to delete a component in JIRA?
To delete a component in JIRA,

Navigate to components screen, hover over the relevant component to display the
Delete button.
You will be prompted to connect these issues with another component if you wish.
36. What are the Version control systems we can integrate with JIRA?
JIRA can be integrated with version control systems such as Git, Subversion, Visual
SourceSafe, etc.,

37. Explain how you can edit multiple issues at the same time?
Editing multiple issues at the same time can be done by performing a bulk
operation. To perform this bulk operation, you will need the global Make bulk
changes permission and the relevant permission for each project.

Bulk operations available in JIRA are as follows

Transition multiple issues through a workflow

Delete multiple issues
Move multiple issues
Edit multiple issues
Watch or stop watching multiple issues
38. What is Zephyr for Jira?
Zephyr for JIRA is an add-on application that provides highly sophisticated test
management capabilities right inside JIRA.

39. What is the importance of JIRA Dashboard? How to create a new Dashboard or
customize the existing dashboard in Jira?
A dashboard is the first page you can see when you logged in to the JIRA
application.
This is a default dashboard that is common for all JIRA users but you can create
your own dashboard as per your requirement.
You can design your personal dashboard by adding different gadgets.
Follow the below steps to create a dashboard in JIRA.

Login to your JIRA account using valid credentials

Choose the Jira icon > Dashboards
Click ••• and choose Create dashboard to create a blank dashboard. You can also
choose Copy dashboard to create a copy of the dashboard you are currently viewing
Create dashboard page is displayed
Name your dashboard and add a description
Fill out the remaining fields and click Create
Note: Dashboard can be edited, copied, shared and deleted from the manage dashboard
section

40. How to add Gadgets to a dashboard in JIRA?

You must be a JIRA admin to add a gadget to a dashboard in JIRA. Some applications
allow dashboards that are shared by groups of people. If you have permission to
update a shared dashboard, the other people sharing the dashboard will see your
changes too.

Following are the steps to add a gadget to a dashboard:

Go to the dashboard by selecting the Dashboards link in the navigation bar.

Click Add Gadget on the dashboard.
Use the gadget wizard to pick the gadgets you want to add.
41. What is a Kanban board in JIRA?
A Kanban board in JIRA is a board that was created using either the Kanban preset
or the DIY option. If a team’s focus is on managing and constraining their work-in-
progress then Kanban board is suitable for them.

42. What is a Scrum board in JIRA?

A Scrum board in JIRA is a board that was created using the Scrum preset. If a team
is planning to work in sprints then Scrum board is suitable for them.

43. What is a validator in JIRA?

Validators in JIRA check that any input made to the transition is valid before the
transition is performed. The issue will not progress to the destination status of
the transition when a validator fails.

44. What is an issue collector?

An issue collector in JIRA allows you to easily embed a JIRA feedback form into
your own website. This helps website visitors to log issues into JIRA through your
website. Visitors to your website do not require a user account in JIRA to use the
JIRA feedback form.
45. What is an Audit log?
The audit log in JIRA allows administrators to look back at changes that have been
made in your site. Audit log helps you in troubleshooting a problem.
https://career.guru99.com/top-18-jira-interview-questions/

Top 35 JIRA Interview Questions & Answers

Following are frequently asked JIRA testing interview questions in for freshers as
well as experienced QA professionals.

1) What is JIRA?

JIRA is an issue tracking product or a software tool developed by Atlassian,

commonly used for bug tracking, project management, and issue tracking; it is
entirely based on these three aspects. It is widely used in software development
and software testing.

2) What is a workflow?

Workflow is defined as a movement of the bug/issue through various stages during

its life-cycle

Created/Open
WIP ( Work In Progress)
Completed/Closed

3) What can be referred to as an issue in Atlassian JIRA?

In JIRA, an issue can be anything like a

Software bug
The project task
A help-desk ticket
The leave request form

4) List out the source control programs with which it integrates?

It integrates with source control programs such as CVS, Git, Subversion, ClearCase,
Visual SourceSafe, Mercurial, and Perforce.

5) Why use JIRA software?

The reason behind using JIRA is

Upfront and fair licensing policy

Features that is not available elsewhere
Get the latest update on the progress of projects
It runs anywhere and recognized with many famous companies
Easily extensible and customizable

6) Is it possible to access JIRA cloud site via a mobile device?

Yes, it is possible to access JIRA cloud site via a mobile device. You have to use
the URL of the JIRA cloud site in your mobile web browser.

7) Can you disable JIRA mobile for the site?

You can disable JIRA mobile for the site so that users can be unable to operate the
desktop view of JIRA on their mobile device. JIRA mobile comes as a system add-on
and can be disabled at any time.

8) Explain labeling and linking issue in JIRA

Labeling Issue:It enables you to categorize an issue in a more informal way than
assigning it to a component or version. You can then search issues according to the
label.
LinkingIssue: This feature enables you to link an association between two issues on
either on the same or different JIRA servers.

9) Name the types of reports generated in JIRA

JIRA offer reports that show statistics for projects, versions, people or other
fields within issues. Various reports included with JIRA are

Average Age Report

Pie Chart Report
Resolution Time Report
Recently Created Issues Report
Resolved vs. Created Issues Report
Single Level Group by Report
Time Tracking Report
User Workload Report
Workload Pie Chart Report, etc.

10) What is Cloning an Issue?

Cloning as issue allows you to create a duplicate of the original issue so that
many employees can work on a single issue within a single project. The clone issue
can be connected to the original issue. A clone issue holds following the
information

Summary
Description
Assignee
Environment
Priority
Issue Type
Security
Reporter
Components, etc.

11) What are the things not included in cloned issue in JIRA?

Time tracking
Issue History
Comments
12) What is the use of “Move Issue” wizard in JIRA?

The move issue wizard enables you to specify another project in your JIRA instance.
Move wizard permits you to change certain attributes of an issue like

Issue Type:If your issue is a customs issue type and does not occur in your target
project, you must choose a new issue type for your issue
Issue Status:If you have assigned your issue as a custom issue status and it does
not exist in your project, you must select a new issue status for your issue
Custom Fields:If you have determined required custom fields for your issue, which
do not occur in the target project, you must set values for them.

13) How is security setting helpful in JIRA?

JIRA’S security setting restricts access to the issue to only those person who is
allowed to work on the issue or a member of the chosen security level. The security
level of an issue can be set either when the issue is created or when the issue is
being edited

14) How can you share an issue with other users in JIRA?

You can email an issue by using the share option in JIRA. You can also email other
JIRA users a link to the issue by sharing the issue with them or by mentioning them
in an issue’s Description or Comment field.

15) How you can modify multiple bulk issues?

To modify multiple bulk issues, you can use the Bulk Change option from the “Tools”
menu of the navigator. All the issues on the current page can be selected for the
bulk operation. The following list details the available bulk operations like

Workflow Transition
Delete
Move
Edit

16) How you can disable mail notification for Bulk Operations?

To disable mail notification for a particular Bulk Operations, you have to de-
select the “Send Notification” checkbox in the bulk operation wizard.

17) What does an issue change history include?

Issue change history includes

Deletion of a comment
Deletion of a work log
Creation or removal of an issue link
Attachment of a file
Changes to an issue field
18) Explain what does the three color indicates tracking times or duration for an
issue?

Three colors will be displayed representing the amount of time spent behind the
issue

Original Estimate (Blue): The amount of time estimated initially to resolve the
issue
Remaining Estimate(Orange): The remaining amount of time left to resolve the issue
Time Spen or Logged (Green): The amount of time spent so far while resolving the
issue

19) What are some of the popular add-ons for JIRA?

Some popular add-ons for JIRA include,

Suites utilities for JIRA

ScriptRunner for JIRA
Zephyr for JIRA – Test Management
JIRA Toolkit Plugin
Atlassian REST API Browser
Portfolio for JIRA
JIRA Misc Workflow Extensions
Tempo Timesheets for JIRA
JIRA Charting Plugin

20) What is Schemes in JIRA?

Schemes are a major part of JIRA configuration. It is a collection of configured

values that can be used by one or more JIRA project. For instance, Notification
Schemes, Permission Scheme, Issue Type Scheme, and so on. There are a total of
seven types of schemes.

21) What can be configured for the JIRA project and issue type?

You can configure the following things for each pair of an issue type and JIRA
project.

The order of custom fields appears on an issue screen

The workflow of an issue including the statuses
Which custom fields and system an issue can use
Project accessibility
Permissions for what a user can do with an issue
Versions and components available for an issue

22) Is it possible to get back up your JIRA cloud data?

In JIRA, you can take a backup of your JIRA cloud data using Backup Manager. But
only one backup file is stored at a time. The existing backup is overwritten by new
ones.

23) What data can be backed up?

The backup data includes,

Attachments if selected
Users and their group settings
Avatars
Issues

24) Give some useful tips on JIRA Workflow

As such Statuses are global objects in JIRA. Changing the name of the status on one
workflow will change the status on all workflows that use that status
Hover over status or transition to see the relevant transition labels
One cannot clone transitions in the workflow designer
In the workflow designer, one cannot create annotations
Directly you cannot set the issue editable property.

25) What are the limitations when editing an active workflow?

If a workflow is active, you cannot edit the workflow name (only the description)
You cannot delete the workflow steps
A step associated status cannot be edited
You cannot add any new outgoing transition if a step has no outgoing transitions
(Global transitions are not considered).
A step’s Step ID cannot be changed.

26) In JIRA workflow, is it possible to transition an issue back to its previous

status?

Practically, it is not possible to transition an issue back to its previous status.

However, you can use the “on hold” feature to transition an issue back to its prior
status. Here are the steps,

In a workflow, Create a global transition to the ‘On Hold’ state.

Now from ‘On Hold’ status create another transition to every other status you want
to come back to
Since the transition names cannot be the same, add a blank space at the end of it.
Now you don’t want the status transition from the ‘On Hold’ and ‘Done’ to ‘On Hold’
So you will hide the other status “On Hold” by adding the value field condition on
the global transition.

27) What is the role of Validators in JIRA?

The Validators in JIRA checks that any input made to the transition is valid before
the transition is performed. If a validator fails, the issue will not progress to
the destination status of the transition.

28) What types of Post functions are carried out after the transition is executed?

Types of Post functions carried out after transition is executed includes

Adding a comment to an issue
Generating change history for an issue
Updating an issue’s fields
Generating an event to trigger email notifications

29) What is an event in JIRA?

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

30) What is the Audit Log?

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

31) For an Agile project, how user stories in JIRA are created?

For an Agile project to create user stories in JIRA, follow below steps.

Issue type -Epic and Issue type – Story linked to it. In order to do so, in the
‘Create Issue’ page, go to “Configure Fields” and select “Epic link” field to be
included in the issue creation screen.
Or you can have a product backlog by creating a main User story and having various
sub-tasks under it.

32) What is an “issue collector”?

An “issue collector” enables you to easily embed a JIRA feedback form into your own
web site. This helps website visitors to log issues into JIRA through our website.
To use JIRA feedback form, visitors to our website do not need a user account in
JIRA.

33) State the difference between Bugzilla and JIRA?

Bugzilla
JIRA
It is an Open Source
It is a commercial tool

Using Bugzilla might be little complicated for few due to grouping users and
granting permissions For some using JIRA would be more convenient than
Bugzilla

Bugzilla allows you to show/hide the whole custom field or specific values based on
the value of some other field JIRA enables conditional configuration based only
on Type fields and Project.

Bugzilla’s has a powerful advanced search option

JIRA lacks advance-level search options. JIRA has a flexible JQL language (JIRA
Query Language). It enables you to build arbitrary boolean expressions.

Unlike JIRA, Bugzilla allows users to select the initial status of a new issue.
Unlike Bugzilla, JIRA enables you to define multiple workflows which are applied
based on the issue’s Project and Type.

Bugzilla has only one link type: Blocks/depends and a Bug ID custom field
JIRA has configurable link types with user-defined semantics. JIRA enables to link
an issue to any other entity outside JIRA.

34) How you can modify multiple bulk issues?

You can modify multiple bulk issues by using option “Bulk Change” option.

35) What is JIRA dashboard?

JIRA dashboard is a dashboard which you will see when you opens up Jira.

Introduction To JIRA Interview Questions And Answers

Jira is a platform-independent tool that has the capability to get executed across
any operating system platforms. It also supports multiple languages like English,
German, Japanese, etc. The major Databases used by this product for backend support
are MySQL and Oracle and SQL server. It can also be integrated with other tools
like GIT, Clear case, Team Foundation Software, Mercury, etc. It is a closed source
product and also available with a limited-time trial version .it is a licensed
software with free license support for academic projects.

JIRA
Jira is a premiere tracking product developed by an Australian company named
Atlassian. the key tasks accomplished with JIRA are bug tracking, issue tracking,
project management, workflow, and process management. it is basically implied for
tracking bugs and issues related to mobile applications and software development.

Core Features:

JIRA supports a large number of customizable business templates to manage simple

and complex business workflows.
Independent tracking of tasks is possible.
Notifications can be dropped to users in the form of emails, comments, @mention,
etc.
JIRA supports more than 10 languages those are widely used as English (US, UK,
India), French, German, Portuguese, Spanish, Korean, Japanese and Russian.
JIRA supports more a large set of reports to track the progress of a specific time
frame, deadlines, etc. Easy to recognize and produce diverse reports which intern
helps to determine the progress of the team . Configuration of these reports is
comparatively easy and the matrices can be displayed to the users in a much better
manner.
Now, if you are looking for a job which is related to Jira then you need to prepare
for the 2019 Jira Interview Questions. It is true that every interview is different
as per the different job profiles. Here, we have prepared the important Jira
Interview Questions and Answers which will help you get success in your interview.

Below are the 10 important 2019 Jira interview questions and answers that are
frequently asked in an interview. These questions are divided into two parts are as
follows:

Part 1 – JIRA Interview Questions (Basic)

This first part covers basic Jira Interview Questions and Answers.

1) Explain the JIRA workflow?

Answer:
A workflow mentions the series of steps involved in the life cycle of a bug or
issue. they are as follow,

1) CREATE: Create the bug or issue

2) WORK IN PROGRESS: Here the entity enters into the fixed stage where a series of
actions are performed to get this resolved

3) CLOSED: Mentions the close of the entity.

2) Mention the Three Colour indicators?

Answer:
This is the common JIRA Interview Questions asked in an interview. The Colour
indicators in JIRA are Blue, Green, and Orange. they signify the time employed in
troubleshooting an issue.

Blue: It pictures the Original time estimate time for the issue. The field will be
labeled as ‘Estimate’

Orange: The Remaining time for getting the issue resolved. The field will be
labeled as ‘Remaining’

Green: Signifies the overall time spent on the problem of reaching a solution. This
field will be labeled as ‘Logged’

3) Explain JIRA project Key?

Answer:
A three to Four character length item which appears for each and every bug and
issue created in a specific JIRA project. Every project will be associated with a
project jey at the initial stage of creating the project. This Assignation will be
performed by a JIRA administrator. The admin has the ability to change the key
during the project creation process and this key is screened across all instances
of the corresponding project.
Let us move to the next JIRA Interview Questions

4) A short note on JIRA reports?

Answer:
JIRA withholds a classified list of reports to depict the project statistics to the
user. The key process involved in JIRA report creation process,

1) Move to the desired project dashboard where the report has to be created
2) Select the reports tab to view all the possible reports allowed for in JIRA
3) Click on Switch report to view the different report.

these reports are diversified based on their need and attributes as follow

Analyzing issues:

Average Age Report

Created vs Resolved issue Report
Pie Chart Report
Recently created Issue Report
Resolution Time Report
Time Tracking Report
User Workload Report
Version Workload Report
Workload Pie chart Report
Scrum projects:

Sprint Report
Control chart
Burn down chart
Cumulative Flow diagram
Epic Report
Release Burndown
Velocity chart
Version Report
Kanban projects:

Control chart
Cumulative Flow diagram.

5) Change history elements for an Issue?

Answer:
The change history section holds all the information on the change performed, a
person who is involved in the change and the timestamp at which the change was
done. To view change history for an issue open the specific issue, Under activity
section select the history tab. the default records of a change history component
are as follow,

Create and delete of the issue link

Create and deletion of a comment written
Deletion of work log
File attachment and detachment changelog
Issue field level changes

Part 2 – JIRA Interview Questions (Advanced)

Let us now have a look at the advanced JIRA Interview Questions.

6) What is Jira Core, Mention its uses and who are Jira core project
administrators?
Answer:
It is an efficient workflow management system which allows formulating unique
process. this utility allows to both increase and decreases the complexity of the
workflows. this allows implying more importance on the process involved. The beauty
of JIRA Core is that the only constraints on your workflow are your processes

Uses of Jira Core :

Run a t-shirt business

setting up workflows that can manage your internal processes such as your design
process
your sales process, your manufacturing process, and even controlling your stock.
Jira Core Users :

Users are accountable for functioning with particular JIRA Core projects. They can
provide access to the project’s issues based on their permissions, workflow
transition and closing on its completion.

Jira Core Project Administrators:

All the project configurations are managed by JIRA project administrators, they
have the permissions for performing almost all configurations related requests. the
major ones are modifying the look and feel of the project and configuration
changes.

7) Explain Issue creation steps?

Answer:
Step by step process on an issue or a defect creation in JIRA, these issues and
defects are further been fixed by developers. Every issue will be tagged with an
issue ID for reference.

Log into JIRA

Select create option, this will navigate to issue creation page
Enter the following details in the issue creation page:
1) Project Field: Describes the project for which this issue is being raised.

2) Summary: field contains the one line title of the issue which imparts the
critical information about the issue in a summarized way. The more effective the
issue headline, the more you can show the criticality of the issue. Of course, the
headline should be easily understood without any chances of misinterpretation. The
example I have taken here, however, is not much critical.

3) Attachment: Any files or contents related to the issue can be uploaded in this
section.

4) Environment: Specifies the platform or the operating system in which the issue
was encountered.

5) Issue Type: Mentions on the type of the issue determined

6) Reporter: Under whom the Issue is being raised

7) Description: A detailed summary of the issue, it includes statements like an

actual result, expected result etc.

8) Fix version: Filled by the developer who is involved in solving the issue, who
decide the version, the time of completing the issue and the status of the issue.

9) Priority: field defines which issue should be considered first to be fixed.

Tester selects the priority of the issue from the dropdown based on its effect on
the application. This example issue is basically of a Medium priority.

Once the above fields are filled the clicking the create button will generate the
issue active for the developers to work on it and resolve.
Let us move to the next JIRA Interview Questions

8) Can an Issue be assigned to two different people, Explain Cloning issue, then
what are linked issues?
Answer:
JIRA does not support assignation of the same issue under two different people at
the same instance of time. this maintains the stability that one multiple developer
can never be tagged to the same issue ever. But at several instances based on the
intensity and volume of work the issue or bug may generate there could be a
possibility of tagging more than one resources to the same issue. so we can get
this accomplished in JIRA by defining a subtask tagged to a different owner and
then getting a relationship accomplished between the issue involved and this
subtask. Also if a task remains uncompleted due to dependency on an intermediate
one then this may trigger an aging issue and to avoid such scenario, JIRA does not
allow one item to be assigned to more than one people at a time. In agile worlds,
it is always preferable to avoid these kinds of dependencies because it affects the
definition of done for one logical unit.

Issue Cloning: Issue cloning is the process of copying an existing issue, this is
an alternative method which allows several users to work on a single issue, The
process of cloning creates a duplicate with the exact information of the existing
one. , the operation done either on the original issue or clone issue has no effect
on each other. the exception items in the cloning process are

Time tracking
Comments
Issue History
Status and Resolution
the process of issue cloning involves the below steps,
1) Open the issue by using its issue id.
2) If it is not under an existing issue create a new issue
3) On the right-hand side of the issue description screen, you will see “…”.
4)Select it displays the list of options.
5) Click on Clone from the displayed drop down option.
6) The clone issue window will be displayed.
5) We may edit the summary of the issue and click on ‘Create’ button.
7) Now a new issue will be created with the statement ‘Clone added in the summary
of it.

Linked Issues: Linked issues is a different scenario two issues in JIRA are linked
and hold some sought of relationship within them, unlike relationships are drawn
within their sub-entities. Every linked issue may have a definition like “Blocked
by or duplicate”. If you are writing a database procedure which needs access to a
few tables and table access is a separate task, then you can link it. You can say
that it is blocked by this issue. When a project is big and more and a number of
owners are more, we may need multiple items created and can link them and define as
a duplicate. When we are in the process of tracking bugs, it is possible for a
scenario where only when a dependent bug is fixed then the main bug could be
successfully resolved, these kinds of situations can be marked and reported as
“blocks” in JIRA.

9)How to create subtasks in JIRA and explain issue cloning?

Answer:
This is the advanced JIRA Interview Questions asked in an interview. Sub tasking is
the process of splitting an issue into small chunks of tasks and each of these can
be tracked and worked impudently. The parent issue holds detailed information on
all the subtasks created. all these task creation terms are confined to within a
single project. Only if all the root tasks are completed then the primary parent
task can be closed this establishes dependency in the process. the major steps
involved in a sub-tasking process are as follow,

1) Open a parent issue by searching with an issue id or create any new issue id.
2)On the right side of the issue description screen, a small “…” clickable icon
will be displayed. selecting this will display all the elements of it.
3) Click on Create Sub-task from the displayed drop down option.
4)Subtask creation window is displayed
5) enter all the mandatory details like project field, summary, environment etc in
the window and select the create button.
6) This generates the subtask successfully under the respective parent.
7) There are also options available to convert an issue into a subtask as well as
subtask into an issue.

10)Adding Gadgets to JIRA dashboard?

Answer:
Several gadgets can be added to JIRA personal dashboards. The JIRA admin is
responsible for adding a gadget to a default dashboard of a JIRA application. no
other users have permission to add these gadgets to the default dashboard. Several
applications allow sharing of dashboards among a specific set of people, in such
cases if one user makes a change to the dashboard the other people who share the
dashboard could also see the changes.

A process of Adding a gadget to a dashboard,

1) Selecting the dashboard link will navigate the user to the dashboard
2) Select Add gadget button in the dashboard
3) Using the gadget wizard to pick the items preferred for adding
4) We can see a list of these gadgets in Gadgets for JIRA applications.

https://www.janbasktraining.com/blog/jira-interview-questions/

JIRA Interview Questions and Answers

Q1). What is the purpose of JIRA for software testing projects?

JIRA is a popular defect management or issue tracking tools that are quite
beneficial when used along with a proper workflow. Here are a few reasons why
should you use JIRA.

It helps you in tracking the progress of a project on time.

The use-cases in JIRA deliver multiple features like implementation, project
management, or bug tracking etc.
This is easy to customize workflows in JIRA as needed.
Along with bug tracking, you can also check the history of an issue like when it
was created and why?
The best part is that JIRA is a platform independent tool that could run anywhere.

Q2). Explain the workflow of JIRA in detail.

Workflows in JIRA define the steps or stages that are followed by an issue during
its entire lifecycle. The process starts with issue creation then a number of steps
are followed to fix the issue and, in the end, the issue is closed finally after
verification. Refer the diagram below for a better understanding of the
concept.Explain the workflow of JIRA in detail.

Read: Performance Testing Interview Questions & Answers

Q3). How are reports generated in JIRA?
To generate reports for a project in JIRA, you need to follow the given steps –

First of all, navigate to the given dashboard.

On the left-hand side, under the reports tab, you can see the different type of
reports there.
Now click on switch report option to view a different report.
Q4). Name a few reports generated by Kanban projects in JIRA.
The reports generated by any Kanban project in JIRA include cumulative flow diagram
and the Flow Chart.

Q5). Name a few reports generated by Scrum projects in JIRA.

Name a few reports generated by Scrum projects in JIRA

Q6). Name a few reports that are needed for the issues tracking and analysis.

Reports Generated For Issue Analysis

Average Age Report

Created vs Resolved issue Report
Pie Chart Report
Recently created Issue Report
Resolution Time Report
Time Tracking Report
User Work load Report
Version Work load Report
Workload Pie chart Report

Q7). Explain the issue creation process in JIRA step-by-step.

Every time an issue is tracked by the testing team, it needs to be reported quickly
to the development team so that it can be addressed as needed. Here, we will see
how to create an issue in JIRA.

First of all, Login to your JIRA account and you will be directed to default
dashboard quickly.
Once you are on the dashboard, you can see a CREATE button there. As soon as you
click on the button, it will redirect you to the issue creation page.
Here, you need to enter the necessary details as required like Project ID, type of
the issue, summary, reporter field, description field, Priority, fix version,
attachment, or environment etc.
Once you have added all details carefully, now click on the CREATE option to
generate a new issue.
Here, one issue ID will be generated that can be used later to check the progress
of a project.
Q8). Do you know about the color indicators and their significance in JIRA?
For every issue in JIRA, there are three indicators in total. These are Blue,
Green, and the Orange. These colors will show the total time spent to fix an issue.
All the information is given under “Time Tracking” section.significance in JIRALet
us see the significance of each color and refer to the image below for a better
understanding of the concept.

Blue – This color will show the total time given to fix an issue. This is called
the Estimated field too.
Orange – This color shows the total time left to fix an issue. It is label as
remaining.
Green – This color shows the total time invested to fix an issue so far. It is
label as the Logged.
Q9). What the total information available under the change history section in JIRA?
Under the change history section, you can check the details when changes were made
to an issue. It will include the previous changes too so that they can be resumed
back when required. Here, the information is given under the change history section
–

Creation or deletion of a comment or issue link.

Deleting a work log.
How to make changes in the file log.
Changes in the issue fields etc.
Q10). How an issue can be shared in JIRA with other users?
On the issue description page, there is one share option that can be used to share
the issue in JIRA with other users. As soon as you will click on the Share option,
it will ask you the username and email ID that has to be filled.

Q11). Why an issue is labeled in JIRA?

Labeling an issue is important in JIRA to find which category it actually belongs
to. If you wanted to search any issue later then it can be quickly found with the
help of labels only. Labels should be added at the time of issue creation and they
can be modified if required. To check the labels for an issue, you should go under
Details section for complete information.

Read: Differences Between Black Box Testing and White Box Testing
Q12). Define the process for linking an issue in JIRA.
Linking means establishing the relationship between the two. Here are the possible
ways how an issue can be linked in JIRA by the following ways –

It can be connected to another issue.

It can be the copy of an existing issue.
It can be used to block any other issue.
Linking can be done on the same servers or different JIRA servers too.

QA curriculum

Q13). What is the significance of a dashboard in JIRA? How can you create your own
dashboard or customize the existing one?
The first page whatever you see when you logged in to the JIRA application is the
Dashboard. There is one default dashboard that is common for all user but you may
create your own as per the requirement. It may be designed with the help of
different gadgets and customized the same based on preferences. The customized
dashboard could give you more detailed information about an issue that you wanted
to check for a project. To create a dashboard in JIRA, you need to follow the
below-given steps –
First of all, login to the JIRA dashboard with valid credentials.
Now on the left-hand side, choose the option, Create a Dashboard. Here, you can see
multiple options. You can choose copy dashboard option if there are limited changes
only otherwise customize the dashboard as per the requirements.
As soon as, you will click pm the required option, a new dashboard page will open
in front of you.
Here, you should enter all necessary details and click on the Create button in the
end.
Now navigate to the page where you will find multiple options to add gadgets to
your dashboard.
There are a plenty of options to edit or manage the layout of the dashboard in
JIRA.
Keep in mind that any particular Dashboard can be edited, copied, shared, delete
from the Manage dashboard section.
Q14). How to schedule an issue in JIRA?
Scheduling an issue in JIRA is easy where you can add a due date and set the
scheduling permission as well. Under the details section, you can check the due
date and other important information too.

QA Quiz

Q15). How the details for a particular project can be listed in JIRA?
Every project has a list of certain attributes that are displayed under the project
summary section. The list of attributes majorly involves –

Nature of the project,

Keys for the project,
Components and version for the project

https://mindmajix.com/jira-interview-questions-answers

JIRA Interview Questions And Answers

(4.0)
| 14046 Ratings
Bookmark this Post Email this Post 14066
JIRA Interview Questions And Answers
Mindmajix as a team has got enough questions from the trainees who got their JIRA
Training and cracked interviews at various MNCs around the world and successfully
placed. From the collection of JIRA Interview Questions, following are the most
common questions we got are listed to make it easy for those who are willing to
crack the interview with ease. All the answers to those were written by our
professional experienced trainers and are tailored to meet the concepts expected by
the interviewer.

Interview Questions On JIRA

Q1) JIRA Vs Trello
JIRA Trello
Integrations about 100 integration partners about 30 integration partners
Mobile apps Android & iOS Android & iOS
Built by Atlassian Fog Creek Software
Hosting on-premise & cloud-hosted cloud-hosted
Key features Project- & issue tracking Kanban boards
Typical customers SMEs & Enterprises Freelancers & SMEs
Pricing Starting at $10/month free
Additional fees Implementation or training services none
Q2) What is JIRA?
Jira is project management tool, provides platform which is mainly confined with
tracking issues, finding bugs and progress of projects under development. Jira is
developed by Atlassian, Inc an Australian firm.

Note: There is no defined abbreviation for JIRA

Q3) What is referred as issues in Jira?

Any bug or error
New software task
Resolving ticket
Request processed form
Q4) What are few report types available to generate using Jira?
Time tracking
Resolution time
User workload
Pie chart
Resolved vs Created issues and many more.
Q5) What do you mean by JIRA?
JIRA is an open source project used for issue tracking Software that is developed
by Atlassian. It is primarily used in s issue/bug tracking, and in the project
management functions.

Q6) Explain Working with workflows in JIRA?

A JIRA workflow is an arrangement of statuses and transitions that an issue travels
through amid its lifecycle and normally speaks to forms inside your organization.
There are pre-defined built-in workflows that can't be altered; in any case, you
can duplicate and utilize these built-in workflows to make your own.

Workflows in JIRA

Related Page:: Guide for Installing JIRA Applications on Windows

Q7) Define Workflow designer in JIRA

The JIRA workflow designer is a graphical tools that enables you to see the design
layout of your workflow and to make and alter a workflow's procedure and
transitions.

With the workflow designer, you can do:

Oversee status and advances: include, snap and drag, or select to alter properties
(Workflow properties) to rename, or erase (from the workflow yet not JIRA).
Include a worldwide transition that permits each different status in the work
process to change to the chose status. Select Allow all statuses to transition to
this one in the properties board for the transition.
Change the screen that a progress employments. See Working in content mode for
points of interest.
Configure advanced transition choices, for example, triggers, conditions,
validators, and post functions. See the Advanced work process setup page.
Q8) How a service desk works in JIRA
Your client presents a demand to your service agents through an entryway or by
means of email.
An service desk sees the demand in their Jira Service Desk line and investigates
the issue.
Your client and different members utilize the entry or email to talk about the
demand with your service desk agent, who works in Jira Service Desk.
Your specialist finishes the demand and your client is fulfilled!
JIRA service desk

Related Page:: Learn JIRA Version History.

Q9) How define JIRA Component?

Components are sub-segments of a project. They are utilized to assemble issues
inside an undertaking into littler parts.

Dealing with a project's components

Sign in to JIRA as a project admin.

JIRA Components

Choose Settings > Projects > and tap the name of a project. The Project Summary
page will appears.
Choose Components in the left menu. The Components page is shown, demonstrating a
rundown of Components and every Component's information.
Q10) How to delete a component in JIRA?
On the 'Components' screen, float over the significant Component to show the Delete
option.
You will be provoked to connect these issues with another Component on the off
chance that you wish.

Q11) Explain Cloning an Issue in JIRA?

Cloning, or copying, an issue that allows you for rapidly making a copy of an issue
inside a similar project. The clone issue is a mirror image of the original issue,
containing a similar data put away in the original issue — e.g. Summary, Affects
Versions, Components, and so on. The clone issue can likewise be connected to the
original issue.

A clone issue is a different element from the original issue. Tasks on the first
issue have no impact on the clone issue and the other way around. The main
connection is a link – if made – between the original issue and the clone issue.

Cloning an Issue retains:

Summary
Description
Assignee
Environment
Reporter
Components
Affects Versions
Fix For Versions
Priority
Issue Type
Security
Attachments
Issue Links
Project
Here are the issues that are cannot be cloned:

Time tracking
Issue history
Comments and
Links to Confluence pages
Jira Sample Resumes! Download & Edit

Q12) Explore the steps to create a Clone Issue?

Open the JIRA issue that to want to be cloned.
Select More > Clone.
JIRA Clone Issue

Also can edit the Summary of clone issue, if required.

In case, issue contains links to other issue(s): Select > In new clone issue as if
or not to include the links.
In case, issue contains sub-tasks: Select > In new clone issue as if or not to
create the sub-tasks.
In case, issue contains attachments: Select > In new clone issue as if or not to
include the attachments.
Click on Create button.
Q13) What does cloning issues mean?
It is process of creating duplicate issue with original one in order to assign the
issue to multiple users to resolve. This cloned issue will have important
attributes like summary, description, issue type, priority, etc., of the original
issue to ensure it is resolved in the end.

Q14) What information is not recorded into cloned issue from original one?
Comments, time tracking and history of the issue are not carried to the cloned
issue.

Q15) What are schemes in Jira?

Schemas define set of values that can be used as Jira project configurations. One
set of schema can be used for one or more project configurations.

Q16) How many types of schemes exist in Jira?

There are seven types of Jira Schemes

Notification
Screens
Permissions
Workflows
Field configurations
Issue types
Custom fields
Q17) Can we backup data in Jira Cloud?
Yes, Jira provides backup functionality of data. But it can save backup file only
once and next time when you backup, the existing data will be overwritten.

Q18) What kind of data can be backup?

Issues, Avatars,users and their setting, and attachments that can be backup.

Q19) Can you delete workflow steps while active?

No

Q20) Can you change step ID for active workflow?

No

Q21) What does validator do?

Validators take care of the inputs to be provided for any transaction. Without
valid approval for the inputs from validators, one cannot complete transaction.

Q22) What is issue collector?

A feedback form provided to collect issues or bugs in the website that are to be
addressed by the customers of the website is one of the feature provided by Jira.
And to address bugs, users no need to have Jira registration.

Q23) What is audit log?

Log file to save all the information about the issue.

Q24) What information is stored in issue change history?

Creation and deletion of issues, deletion of comment, attachments and issue field
changes are saved.

Q25) How can you perform bulk operations on issues?

Jira provides option to execute bulk operations. Select Bulk Change option from the
tools menu, and then you can perform transition, delete, move or edit option for
all the issues in the current page.

Q26) What to do if you don’t want to perform bulk operations on mail notification
issues.
In the bulk operations wizard, you need to uncheck the email notification to
disable.

Q27) How can you track time spent on issue?

Issue tracking is made easy with three different colors representing three
different status of an issue.

Blue color - Estimated time to resolve issue

Orange color - Remaining time to resolve issue
Green color - Total time spent(Logged In) to resolve the issue.
Q28) What is scheduling an event in Jira?
Scheduling an event is activated in order to trigger action with respect to issue.
And to perform this scheduling, one should request “Schedule issue permission” from
the administrator. This provides “due date” to an issue to be scheduled for.

Q29) What are field configurations?

Set of instructions given as configuration to Jira to define a field’s behaviour
like necessity of fields, field visibility, etc.

Q30) What do you mean an Issue in JIRA?

Various organizations utilize JIRA to track various types of issues. Contingent
upon how your organization is utilizing JIRA, an issue could represent to a product
bug, a project assignment, a helpdesk ticket, a leave request form, and so forth.

You can get to an issue in JIRA from a query result or from a dashboard gadget that
gives access to issues.
In genreal A JIRA issue looks like this: