Devops Jira Interview Questions and Answers Pdf

Jira Interview Questions

Companies around the globe are frequently choosing the DevOps culture and by the period of 2016, 25 percent of best global 2000 companies have used DevOps as a mainstream approach according to Gartner. If you are a DevOps engineer with vital knowledge of devices, methods, and utilization of technology, be guaranteed that 2018 is going to be your time. This bug tracking device is not just applied for convenience-related characteristics like reporting, recording, however, is further combined straight with code improvement background. JIRA is an active device and possesses the ability to pursue any variety of defects/issues. Agile projects are also recommended by JIRA.

Considering DevOps is a developmental approach and not just a kit of automation devices, companies believe about the essential interpersonal talents that perform DevOps practitioners strongly. Cross-team interaction and collaboration policies may be difficult to bring across the table, then professional competencies, though they’re neither less significant. Instantly, above was the basic explanation of Atlassian JIRA, defect tracking device. Within this section, we will present multiple interview question and answers which will improve you know this device extremely beneficial as well as on the other hand will accommodate perfectly to your interview.

If you intend to deliver an interview for a DevOps-centric role, here is a whole listing of the common successful DevOps interview questions. If you have visited DevOps interviews or have any further questions you would like us to respond, please do suggest them in the commentaries segment beneath.

1. What Is JIRA?
Answer: A software device or an issue tracking product promoted by Atlassian is known as JIRA, generally utilized for bug tracking, issue tracking and project management; it is totally based on these three features.

2. Explain what is a workflow?
Answer: A movement of the issue/bug for different stages during its life-cycle is called workflow.

WIP (Work In Progress)

3. What can be referred to as an issue in JIRA?
Answer: In JIRA, a problem can be anything like a

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

4. List out the source control programs with which it integrates?
Answer: It combines with source control programs so as Subversion, CVS, Visual SourceSafe, Git, ClearCase, Perforce and Mercurial.

5. Why use JIRA?
Answer: The purpose of using JIRA is

Features that are not available elsewhere
Upfront and fair licensing policy
Easily extensible and customizable
Get the latest update on the progress of projects
It drives everywhere and identified with several leading businesses

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

7. Can you disable JIRA mobile for the site?
Answer: 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 the labeling and linking issue in JIRA?

Labeling Issue: You can then search for issues according to the label. It permits you to classify an issue in a major informal process than attaching it to a version or component.
Linking Issue: This characteristic permits you to combine a connection among two problems on either on the same or separate JIRA servers.

9. Mention the types of reports generated in JIRA?
Answer: JIRA proposition reports that display statistics for projects, people versions, or different areas inside issues. Multiple reports involved with JIRA are

Average Age Report
Pie Chart Report
Single Level Group By Report
Time Tracking Report
Resolution Time Report
User Workload Report
Recently Created Issues Report
Resolved vs. Created Issues Report
Workload Pie Chart Report, etc.
10. Explain what is Cloning an Issue?
Answer: The clone issue can be correlated to the initial issue. Cloning as issue permits you to build a duplicate of the original issue so that multiple operators can work on a particular issue in a particular project. A clone issue includes the following information

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

11. Enlist 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 Workload Report
Version Workload 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 the desired project dashboard.
Click on Reports tab from the left-hand side to view different reports.
Click on Switch report to view the different reports.

12. Explain step by step 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 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 the ‘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 the Project field, a 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 the 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.

The 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 the 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 of 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 they 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 the Attachment field, any video or screenshot related to the issue is being uploaded.

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

4) After all the details have been completed, click on the ‘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.

13. 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 the ‘Time Tracking’ section. Each color 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’.

14. 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 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 in history for any issue can be viewed in JIRA by following steps:

Open any particular issue.
Click on the ‘History’ tab present in the ‘Activity’ section.

15. 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. 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.

16. 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

17. 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 to 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 issue section contains the drop-down 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.
Linking of issues can be done either on the same or different JIRA servers.

18. What is the purpose of the 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 in steps how a personal dashboard can be created:

Enter valid credentials and get navigated to JIRA dashboard.
Click on “…” displayed on the upper right-hand side and choose the option ‘Create dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the currently viewed dashboard.
‘Create Dashboard’ page is displayed.
Enter all mandatory information and click on the ‘Create’ button.
After creating a dashboard, you get navigated to a page where there are multiple options to select and add gadgets to your dashboard.
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.

19. 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.

20. 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. These attributes include:

Name of the project
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 this image will give you a clear idea.

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.

21.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 the 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 below in the figure.

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

22. 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.

Open a parent issue by searching with an issue id or create any new issue id.
On the right-hand side of the issue description screen, you will see “…”. Click on it and options are displayed.
Click on Create Sub-task from the displayed dropdown option.
Create a sub-task window is displayed.
Enter all the mandatory details and click on ‘Create’ button.
Now the created subtask gets added to the parent issue under sub-task section
There are also options available to convert an issue into a subtask as well as sub-task into an issue

23. 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 the 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
Issue History
Status and Resolution
Let us see how to create a clone of an issue:

Open any issue by searching for an issue id or create any new issue id.
On the right-hand side of the issue description screen, you will see “…”. Click on it and options are displayed.
Click on Clone from the displayed drop-down option.
Clone issue window is displayed.
If required, you can edit the summary of the issue and click on the ‘Create’ button.
Another issue is created with ‘CLONE’ added in the summary.

24. Explain Kanban board?
Answer: Kanban boards are created for the projects where the team has its prime focus on visualizing the workflow and managing the project’s work in progress. The most important feature of the Kanban board is that it is found in work mode because the projects do not have their work as planned.

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

Log In to the JIRA application using valid credentials and get navigated to the dashboard.
Click on Project drop-down and select the option ‘Create Project’.
Select ‘Kanban Software development’ and click on Next button.
Enter all the necessary details and click on the Create button.
Kanban board is created as shown in the below example.
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.

25.Mention one similarity and one difference between JIRA Scrum and JIRA Kanban?

Similarity: Both JIRA Scrum and Kanban are considered as the most powerful process tool for the optimization of work and the processes as both processes focus is on continuous optimization and visualizing the workflow. In these cases, large and complex tasks are broken down and each individual tasks are worked on and completed efficiently.
Difference: Scrum board is the work mode where the progress of sprints and tracking of its work is done. Here the team determines the list of issues that have become backlog and then these issues are moved to sprints as per team plan.
In the case of the 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.

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

User snap
Pager Duty
Tempo Timesheets

27.what comes under JIRA Schema?
Answer: JIRA Schema consists of the following:

Issue types
Custom fields
Field configurations

28. How is the security setting helpful in JIRA?
Answer: Security setting for any issue is defined or say set either at the time of the 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 access of the issue to the member of the chosen security level.

29. Is It Possible To Access Jira Cloud Site Via A Mobile Device?
Answer: Yes, it is possible to access JIRA cloud site via a mobile device. You have to just use the URL of the JIRA cloud site in your mobile web browser.

30. Can You Disable Jira Mobile For The Site?
Answer: 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.

31. Explain How You Can Disable Mail Notification For Bulk Operations?
Answer: To disable mail notification for a particular Bulk Operations, you have to de-select the “Send Notification” checkbox in the bulk operation wizard.

32. Explain How You Can Share An Issue With Other Users?
Answer: 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.

33. Explain What Does The Three Color Indicates Tracking Times Or Duration For An Issue?
Answer: Three colors will be displayed representing the amount of time spent on the issue:
Original Estimate (Blue): The amount of time originally estimated 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

34. Mention What Can Be Configured For Jira Project And Issue Type?
Answer: 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

35. Mention Is It Possible To Get Back Up Your Jira Cloud Data?
Answer: 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.

36. Mention Some Useful Tips On Jira Workflow?
Answer: 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

37. Mention What Is The Role Of Validators In Jira?
Answer: 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.

38. What Is An Event In Jira?
Answer: The events are classified into 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.

39. State What Data Can Be Backed Up?
Answer: The backup data comprises:

Attachments if selected
Users and their group settings
40. What Is Audit Log?
Answer: you can see all the details about the issue created, and the changes made in the issues Under Audit Log.

Note: Browse latest Devops Interview Questions and Devops training videos. Here you can check Devops Online Training details and Devops Training Videos for self learning. Contact +91 988 502 2027 for more information.

Leave a Comment

Scroll to Top