JIRA Interview Questions

JIRA is a defect tracking tool that is used for tracking bugs. Atlassian is the developer of this software. JIRA is commonly used as an incident management tool to manage projects while keeping track of defects and issues. Over the years the demand for tool from the enterprises has increased, thus the demand for JIRA technicians has also seen an increase.

In the field of programming, there will be always a need to employ a programmer who knows everything about Jira. For this reason most interviews will be based on Jira knowledge. In fact you will find more Jira interview questions than by other questions in other sections of programming. This is a very important reason why you should make a good preparation before you go out for the interview.

 

So below are a series of JIRA interview questions you are likely to be asked when sitting for an interview. These JIRA interview questions will help you ace the interview while also providing you with basic knowledge of the software. While the knowledge of these JIRA interview questions will help, it is crucial that you are confident in yourself to impress the interviewers. These questions have been asked for a long time and they just never fade away because they are must-ask questions. The sample answers are provided as a guideline on how they can be answered. You should also keep in mind that these questions might not come in oral form as you may expect. Mostly you may be given a test with Jira interview questions to attempt just to gauge your knowledge.

1. What is JIRA?

Atlassian JIRA is an issue tracking software that is commonly used for project management, bug tracking, and issue tracking. The software deals specifically with only these three issues and are widely used across the globe for software testing and development. The name JIRA originated from “Gojira”,  “Gojira” is popularly known all over the world as Gozilla.

2. Explain the workflow of JIRA ?

Workflow is the series of stages a bug goes through in its lifetime. The workflow includes the creation of the bug, a series of steps taken to fix the bug and closing the bug after verification.

3. What is considered to be issued in Atlassian JIRA?

In Atlassian JIRA, the following are considered to be issues

  • A leave request form
  • A project task
  • A bug in the software
  • Help-desk tickets

4. What are the advantages of using JIRA?

The reasons behind JIRAs dominance in its sector are

  • Unique features that are only available in JIRA
  • Has many extensions and highly customizable
  • It has a fair and upfront licensing policy
  • It is recognized by many leading companies
  • It can be run anywhere as it is platform-independent
  • It allows you to track the progress of your project from time to time.

5. What are the three color indicators in JIRA and what do they indicate ?

Any issue in JIRA uses the three colors blue, green and orange to indicate the amount of time that has been spent on it. All this information is available under ‘Time Tracking’ section and each color has its own significance

  • Blue: This color denotes the original estimated time. It is the initial estimate by the system about how much time it will take to resolve the issue. It is labeled as ‘Estimated’
  • Green: This color denotes the actual amount of time that has been spent in resolving the issue so far. It is labeled as logged.
  • Orange: This color denotes the amount of time left before the issue is resolved. It is labeled as ‘Remaining’

6. How would you share an issue with other users in JIRA?

You can share an issue in JIRA by using the share option in the issue description page. You could either directly email the issue or get a link that you can share via email. This link will open the issue for the receiver.

7. How are issues linked to JIRA?

You can link various issues in JIRA, this establishes a relationship between the linked issues. An issue can be linked with another issue on the same server or a different JIRA server. An issue can be linked to another issue in the following ways

  • One issue might block another issue
  • An issue might relate to another issue
  • An issue might duplicate another issue

8. How can you schedule an issue in JIRA?

You can schedule an issue by filling its Due date field. This can be done when you create the issue or midway during the process in the settings. Only privileged users with schedule issues permission can alter the due date field.

9. What is cloning an issue in JIRA?

Cloning an issue lets you create a duplicate of an issue within a single project. This lets more than a single employee work on the same issue. Changing the clone does not affect the original issue. A cloned issue retains the following information :

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

However, the clone does not retain the following information:

  • History of the issue
  • Comments made on the original issue
  • Time tracking of the original issue

10. How does the security setting help you in JIRA?

JIRA lets you assign each issue a specific security level. Only members of the chosen security level will be able to work on the issue. The security level can be introduced while creating the issue or midway through its workflow.