JIRA Complete Notes & Interview Guide

1. What is JIRA?

Item Description
Tool Project Management & Issue Tracking Tool
Developed By Atlassian
Purpose Agile Project Management, Sprint Management, Issue Tracking
Used By Developers, QA, Scrum Masters, Product Owners, Business Analysts
Supports Scrum, Kanban, Bug Tracking, Release Management
Current Name Jira Software

2. Why JIRA is Used

Purpose Example
Requirement Tracking User Stories
Defect Tracking Bugs
Sprint Planning Sprint Backlog
Task Management Development Tasks
Agile Reporting Burndown Charts
Release Tracking Version Releases

3. JIRA Architecture

Project ? Epic ? Story ? Task / Sub-task

4. JIRA Hierarchy

Level Description
InitiativeLarge business objective
EpicLarge feature
StoryUser requirement
TaskTechnical work
Sub-taskSmall activity
BugDefect
SpikeResearch activity

5. JIRA Issue Types

Issue Type Purpose
EpicLarge feature
StoryFunctional requirement
TaskDevelopment work
BugDefect
Sub-taskChild task
SpikeInvestigation work

6. Epic, Story, Task, Sub-task, Bug & Spike

Epic Example

Online Shopping Application • Login • Search Product • Cart • Checkout

Story Example

As a customer, I want to search products So that I can purchase items.

Task Example

Create Product Search API

Sub-task Example

• Create Controller • Create Service Layer • Write Unit Tests

Bug Example

Login page throws HTTP 500 error.

Spike Example

Investigate OAuth2 Integration.

7. JIRA Workflow

To Do ? In Progress ? Code Review ? Testing ? Done

8. Status Definitions

Status Meaning
To DoNot Started
In ProgressDevelopment Started
In ReviewCode Review
TestingQA Testing
DoneCompleted
BlockedWaiting on Dependency
ReopenedIssue Returned

9. Sprint Lifecycle

Create Sprint ? Sprint Planning ? Start Sprint ? Daily Standups ? Sprint Review ? Sprint Retrospective ? Close Sprint

10. Scrum Board

Column Purpose
BacklogPending Work
To DoSprint Work
In ProgressDevelopment
TestingQA Validation
DoneCompleted Work

11. Kanban Board

Backlog ? Ready ? Development ? Testing ? Done
Feature Description
Continuous FlowNo Sprint Required
WIP LimitRestricts Active Work
Pull ModelTeam Pulls Work

12. Story Points

Story Point Complexity
1Very Small
2Small
3Medium
5Moderate
8Complex
13Very Complex
21Epic

13. Components, Labels & Fix Versions

Components

UI Backend Database Security

Labels

jwt springboot payment production

Fix Versions

v1.0 v2.0 v3.0

14. Priority Levels

Priority Meaning
HighestProduction Down
HighMajor Functionality Impact
MediumNormal Defect
LowMinor Issue
LowestCosmetic Issue

15. Severity vs Priority

Severity Priority
Technical Impact Business Importance
Defined by QA Defined by Product Owner / Business

16. Assignee vs Reporter

Field Meaning
Reporter Person who created the issue
Assignee Person responsible for fixing it

17. Common JQL Queries

Use Case JQL
Find Open Bugs project = BANK AND issuetype = Bug
Assigned To Me assignee = currentUser()
Open Issues status != Done
Current Sprint Sprint in openSprints()
High Priority Bugs priority = High AND issuetype = Bug

18. JIRA Reports

Report Purpose
Burndown ReportSprint Tracking
Velocity ReportTeam Capacity
Sprint ReportSprint Summary
Epic ReportEpic Progress
Cumulative Flow DiagramWorkflow Efficiency
Control ChartCycle Time Analysis

19. Frequently Asked JIRA Interview Questions

Question Answer
What is JIRA?Agile project management and issue tracking tool.
What is an Epic?Large feature containing multiple stories.
What is a Story?User requirement from business perspective.
What is a Sprint?Time-boxed iteration.
What is Story Point?Relative estimation unit.
What is JQL?Jira Query Language for searching issues.
What is Velocity?Story points completed in a sprint.
What is Burndown Chart?Shows remaining sprint work.