Q#1)What is Jira?
Answer: 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.
Q#2) 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:
Q#3) Explain the 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, a 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:
Q#4) 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:
Following are the examples of reports generated for Scrum projects:
Following are the examples of reports generated for Kanban projects:
For generating reports for your project, follow the below steps;
Q#5)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 of how an issue is created in Atlassian JIRA.
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 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 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.
Q#6)For any particular issue what are all 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:
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.
When share option for any particular issue is clicked, it contains the link to the issue to be shared along with the ‘Username or Email’ and ‘Note’ field that has to be filled.
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.
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:
For displaying the details of the Linked issues, there are two fields available in JIRA: ‘Linked issues’ and ‘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.
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 of 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 the option ‘Create dashboard’. You can also choose ‘Copy dashboard’ in the case of copying the currently viewed dashboard.
3) ‘Create Dashboard’ page is displayed.
4) Enter all mandatory information and click on the ‘Create’ button.
5) After creating a dashboard, you get navigated to a page where there are multiple options to select and add gadgets to your dashboard.
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.
These attributes include :
Q #13) Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.
Answer: 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.
Q #14) What are the most useful JIRA add-ons.
Answer: Some of the most useful JIRA add-ons are listed below:
Q #15) What comes under JIRA Schema?
Answer: JIRA Schema consists of the following:
Q #16) How is a 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.
Q#17)What are the issue 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 in the below 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:
Q#18)How is 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.
4)Create a sub-task window is displayed.
5) Enter all the mandatory details and click on the Create button.
6)Now the created subtask gets added to the parent issue under sub-task section as shown below in the figure:
7) There are also options available to convert an issue into a subtask as well as subtask into an issue.
Q#19)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:
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.
4) Clone issue window is displayed.
5) If required, you can edit the summary of the issue and click on the Create button.
6) Another issue is created with ‘CLONE’ added in the summary.
Q#20)Explain the 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.
1) Log In to the JIRA application using valid credentials and get navigated to the dashboard.
2) Click on Project dropdown and select the option Create Project.
3) Select Kanban Software development and click on Next button.
4) Enter all the necessary details and click on the Create button.
5) Kanban board is created as shown in the below example.
Note: I have just taken a basic 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#21)What are the differences between JIRA and Bugzilla?
Answer : JIRA and Bugzilla are the two bug tracking tools that are widely being used by several organizations for quite some time now.
|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 Bugzilla|
|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 linking 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 defining 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|
Q#22)Can Jira be used for test case management?
Answer : 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)
Q#23)What are the limitations when Editing an Active Workflow?
Answer : Limitations apply when editing the draft for an active workflow:
Q#24)What is a workflow designer in Jira?
Answer : 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.
Q#25)How does service Desk work in Jira?
Answer : Here is how Customers and Service desk agents work together to resolve a request in JIRA.
Q#26). What are the color indicators in JIRA and mention their significance?
Answer : There are three colors (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