Jira Interview Questions and Answers

Sprint report can be seen by doing the following steps:-

• Click on the JIRA icon
• Click on Projects and then select the relevant project
• Click on Reports and then select ‘Sprint Report.’
• Now, Select the relevant sprint from the sprint drop-down

A workflow in JIRA is a series of following tasks which are participating in the life cycle of a bug or an issue.

• Create: Create an issue or bug
• Work in progress: They are a series of actions that are performed to fix the problem
• Closed: Completion of the issue after verification Workflow represents the business processes.

Each of the JIRA application has default issue types. The user can create new issue types or use the default issues depending on the project.

There are two types of default issue types of JIRA core:-

• Task – Task that needs to be completed
• Subtask – Smaller task inside a big task
• There are four types of default issue types of JIRA Service Desk:-
• Incident – System outage or incident
• Service request – It is General request from a user for a product or a service
• Change – Roll out of the new technologies or the new solutions
• Problem – Track underlying causes of incidents

There are three types of default issue types of JIRA Software:-

• Story – Functionality request declared from the view of the user
• Bug – It is a problem that impairs a product or a service functionality
• Epic – IT is a large piece of work that cover many issues

Issues are basically the building blocks of a JIRA project. An issue represents a bug or error, software task, a story, leave request form, help-desk ticket or any another issue type in the project. Many organizations use JIRA to track different types of issues.

A story points in JIRA represents the difficulty level of the given account. Story points can be expressed as the Fibonacci sequence ( 1,2,3,5,8,13,….100), the linear scale (1, 2, 3, 4….), the Powers of 2 (1, 2, 4, 8……)

Cloning in JIRA is a process in which the clone or the replica of the original issue is created so that the multiple users can work at the same time on the same issue within the same project. The clone contains the same information which is stored in the original issue. The operation which is done on clone issue has no effect on the original question; they both are independent. The information clone holds are:-

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

The information that a clone cannot copy from the original issue are:-

• Time tracking
• Comments
• Issue history
• Status and Resolution

Point to be noted: Go through this Q&A very thoroughly as this is one of the critical JIRA tool interview questions.

Some of the popular JIRA add-ons are:-

• Jenkins-CI
• Usersnap
• Slack
• HipChat
• GitHub
• PagerDuty
• Tempo Timesheets
• ScriptRunner
• Portfolio
• Atlassian REST API Browser

An “issue collector” enables the user to embed a JIRA feedback form into the user's own website. As a result, visitors are able to log issues or bugs into JIRA through the site. Besides that, the website visitors need not make an account in JIRA to fill up the JIRA feedback form.

A bug report can be created by the following steps:-

• Login into the JIRA account
• Click on the CREATE tab on the upside menu bar to create an Issue.
• ‘Create Issue’ window will appear on the screen
• Select the project in which there is a bug and add issue type as Bug.
• Fill up the complete form like Summary, Description, Priority, Environment, Attachment, Assignee and Status.
• Click on create to report the bug.

This is the favorite interviewer question in JIRA questions.