In this blog, we will be covering the most frequently asked JIRA interview questions with detailed answer for your reference. JIRA is a bug tracking and defect management tool that is that has been used by software testing team from years. The tool was developed by Atlassian that is necessary for issue tracking and project management too.
The tool can be directly integrated into the code development environment for agile project management, recording, reporting, or any other convenient-related feature. Once you know what is Atlassian JIRA tool, let us focus on a list of 15 interview questions and answer to help you in your next interview.
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.
Read: Why is Performance Testing Important?
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.
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. Let 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: What Lies Behind My Decision To Become A Software Tester?
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.
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.
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
That’s all for the day. We have listed top 15 JIRA interview questions here with detailed answers for your reference. We make sure that a depth understanding of these questions will surely help you in getting selected by top MNCs quickly.
Read: Top 20 Advanced API Testing Interview Questions and Answers
Testing Vs. Different Technologies
- AWS & Fundamentals of Linux
- Amazon Simple Storage Service
- Elastic Compute Cloud
- Databases Overview & Amazon Route 53
9 days 02 Feb 2020
- Intro to DevOps
- GIT and Maven
- Jenkins & Ansible
- Docker and Cloud Computing
3 days 27 Jan 2020
- Data Science Introduction
- Hadoop and Spark Overview
- Python & Intro to R Programming
- Machine Learning
0 day 24 Jan 2020
- Architecture, HDFS & MapReduce
- Unix Shell & Apache Pig Installation
- HIVE Installation & User-Defined Functions
- SQOOP & Hbase Installation
1 day 25 Jan 2020
- Salesforce Configuration Introduction
- Security & Automation Process
- Sales & Service Cloud
- Apex Programming, SOQL & SOSL
4 days 28 Jan 2020
- Introduction and Software Testing
- Software Test Life Cycle
- Automation Testing and API Testing
- Selenium framework development using Testing
3 days 27 Jan 2020
- BA & Stakeholders Overview
- BPMN, Requirement Elicitation
- BA Tools & Design Documents
- Enterprise Analysis, Agile & Scrum
3 days 27 Jan 2020
- Introduction & Database Query
- Programming, Indexes & System Functions
- SSIS Package Development Procedures
- SSRS Report Design
7 days 31 Jan 2020
Receive Latest Materials and Offers on QA Testing Course