Devops Jira Interview Questions and Answers Pdf

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