Jira Fundamentals: Issues, Epics, Projects & Workflows Explained

What is Jira? - Learn Jira Fundamentals

Jira is a project management tool developed by Atlassian.

It is mainly used for:

• Bug Tracking

  Advertisement

• Issue Tracking

• Project Management

• Agile Software Development (Scrum and Kanban)

Jira helps development teams, QA teams, business analysts, and project managers collaborate efficiently by managing work items from creation to completion.

Real-world Example

Suppose your QA team discovers a defect in the login feature.

You create a Jira issue with details like:

Throughout the software development lifecycle, everyone can:

• Track the bug

• Communicate

• Add comments

• Verify when it is fixed

How QA Uses Jira in Real Projects

As a QA Engineer, Jira is used to:

• Raise defects (bugs)

• Track bug status

• Assign bugs to developers

• Add screenshots, videos, logs, and attachments

• Add comments for communication

• Set priority and severity

• Link bugs with user stories

• Link test cases using plugins like Zephyr or Xray

• Track sprint progress

• Participate in sprint planning and backlog refinement

• Monitor dashboards and reports

Typical Bug Workflow in Jira

Open
   ↓
Assigned
   ↓
In Progress
   ↓
Code Review
   ↓
QA Testing
   ↓
Done / Closed

Some organizations customize their workflows based on their processes.

Bonus Tips

• Supports both Scrum and Kanban Agile methodologies.

• Highly customizable workflows.

• Supports custom fields and issue types.

• Integrates with:

  • Confluence

  • Jenkins

  • GitHub

  • Bitbucket

  • Selenium

  • Zephyr

  • Xray

Interview Answer

"Jira is the primary project management and issue-tracking tool used in Agile software development. In my project, we used Jira to log defects, assign tasks, manage sprints, and track issue progress. Whenever I found a bug during testing, I created a Jira ticket with all necessary details like steps to reproduce, expected result, actual result, screenshots, logs, and severity. We also linked bugs with user stories and tracked sprint progress through Jira dashboards."

What are Issues in Jira?

An issue is the basic unit of work in Jira.

Everything that needs to be tracked in a project is created as an issue.

An issue can represent:

• Bug

• Task

• Story

• Epic

• Sub-task

• Improvement

• Change Request

• Spike

(Depending on the project.)

Real-world Example

Imagine you're testing an e-commerce website.

Different work items can be created as Jira issues.

Example Hierarchy

Epic
├── Story 1
│   ├── Sub-task
│   └── Sub-task
├── Story 2
│   └── Sub-task
└── Story 3

Information Available in Every Jira Issue

Every issue generally contains:

• Issue Key (QA-101)

• Summary

• Description

• Issue Type

• Priority

• Severity (If Customized)

• Reporter

• Assignee

• Status

• Labels

• Sprint

• Epic Link

• Attachments

• Comments

• Linked Issues

• Due Date

• Story Points (Agile)

Bonus Tips

• Every issue has a unique Issue Key.

• Every issue follows a workflow.

• Issues can be linked for traceability.

• Custom issue types can be created based on project requirements.

Interview Answer

"In Jira, every work item is called an Issue. It can be a bug, a story, a task, an epic, or a sub-task. In my previous project, we used stories for new features, tasks for testing activities, and bugs for defects. Every issue had a defined workflow, and we linked bugs with their respective stories to maintain complete traceability."

Epic vs Story vs Bug vs Task vs Sub-task

Jira categorizes work into different issue types based on the nature and size of the work.

Real-world Example (Online Shopping Application)

Epic

Shopping Cart Module

Stories

• Customer can add products.

• Customer can remove products.

• Customer can update quantity.

• Customer can save the cart for later.

Bugs

• Add to Cart button is not working.

• Quantity is not updating.

• Total amount calculation is incorrect.

Tasks

• Prepare Test Data.

Quick Memory Trick

• Epic = Big Goal

• Story = User Feature

• Task = General Work

• Bug = Something Broken

• Sub-task = Small Part of Story or Task

Interview Answer (4+ Years)

"In my project, we structure work using Epics, Stories, Tasks, Bugs, and Sub-tasks. A large module like 'Checkout' is an Epic, broken into Stories such as 'Add Payment Gateway'. Complex Stories are split into Sub-tasks, such as 'Test UPI Payment'; Bugs are logged for defects found during testing; and Tasks cover setup and documentation. This gives clear traceability and cleaner sprint planning."

Issue Types in Jira

Issue types define the nature of a work item.

Real-world Example (E-commerce Checkout)

Epic

Checkout Functionality

Stories

• Add Payment Gateway

• Apply Discount Code

Sub-task

• Test UPI Payment

Bug

• Discount code is not working.

Task

• Create regression checklist.

Project Usage

• Stories are assigned for feature development.

• Bugs are created during testing.

• Tasks cover environment setup and documentation.

• Epics group related stories.

• Sub-tasks divide large work into smaller activities.

Bonus Tips

• Zephyr, Xray, and TestRail introduce Test Case, Test Execution, and Test Cycle issue types.

• Separate workflows can be configured.

• Different icons and colors distinguish issue types.

• Custom issue types can be created.

Interview Answer (4+ Years)

"In my current project, we use different Jira issue types to organize and manage work efficiently. Stories are created for feature development, Bugs are logged for issues identified during testing, and Tasks are used for technical or QA-related activities such as test environment setup and documentation. Related Stories are grouped under Epics like 'User Profile Module', and complex Stories are divided into Sub-tasks. This structure provides better traceability, clear ownership, and improved sprint planning."

What is a Project in Jira?

A project in Jira is a collection of:

• Issues

• Workflows

• Users

• Boards

• Permissions

• Configuration Settings

grouped under a common business goal.

Real-world Example

Each project has its own:

• Workflow

• Issue Types

• Scrum/Kanban Board

• Users and Roles

• Permissions

• Dashboards

• Reports

• Backlog

• Sprint Management

Types of Jira Projects

Bonus Tips

• Every project has a unique Project Key.

• Multiple boards can exist within one project.

• Each project can have separate:

  • Workflows

  • Screens

  • Permissions

  • Custom Fields

• Large organizations often maintain separate projects for Web, Mobile, API, UAT, and Production Support.

Interview Answer (4+ Years)

"In my current project, we maintain separate Jira projects for different applications such as Web, API, and Mobile. Each project has its own workflows, issue types, Scrum board, and sprint backlog. As a QA Engineer, I primarily work within the Web project, where I create and manage Stories, Tasks, and Bugs, participate in sprint planning, update issue statuses, and monitor progress through Jira dashboards. This separation helps teams manage work efficiently while maintaining clear visibility and traceability."

What is a Workflow in Jira?

A workflow defines the lifecycle of an issue.

It controls:

• Statuses

• Transitions

• Rules

• Conditions

• Validations

Real-world Example

Open
   ↓
In Progress
   ↓
In Review
   ↓
Ready for QA
   ↓
Closed

Real Usage

Each issue type can have its own workflow.

QA Workflow Example

Test Case Created
        ↓
In Review
        ↓
Ready for Execution
        ↓
Passed / Failed

Bug Workflow Example

New
   ↓
Assigned
   ↓
Fixed
   ↓
Verified
   ↓
Closed

Bonus Tips

• Workflows are visible on Jira boards.

• Admins can customize workflows.

• Workflow automation supports auto-assignment and auto-closing.

Interview Answer

"In Jira, workflows help us control how issues move across different stages. In my project, we customized workflows to include 'Ready for QA' and 'Blocked' statuses, which were critical for tracking test dependencies. Every issue, whether a bug or a task, followed a structured process from creation to closure. For example, no bug could be marked as 'Done' without moving through a 'Ready for QA' stage, which enforced testing review."

What is the Backlog in Jira?

A backlog is a list of tasks, user stories, bugs, and other issues that have not yet been started.

It acts as the team's to-do list.

Analogy

Like a grocery list.

Everything is written down first and later selected when needed.

Real Usage

• New bugs

• Enhancements

• Test tasks

are first added to the backlog.

Product Owners prioritize them before sprint planning.

QA engineers can filter backlog items for testing work.

Example (QA Perspective)

Backlog Items:

• Story – Implement Login Functionality

• Task – Create Login Test Cases

• Bug – Login button not clickable

• Story – Implement Forgot Password

• Task – Test Forgot Password Flow

All remain in the backlog until selected for a sprint.

Bonus Tips

• Backlogs are available in Scrum projects.

• Items can be filtered by:

  • Issue Type

  • Assignee

  • Labels

• Backlog Grooming (Refinement) is conducted regularly.

Interview Answer (4+ Years)

"In our project, we used the Jira backlog to manage all pending work. The QA team often referred to the backlog to see which stories or bugs were ready for testing. We conducted weekly backlog refinement meetings where QA, developers, and the Product Owner discussed each item's priority, testability, and effort estimate. This helped us pick the right issues for upcoming sprints and not miss any critical test areas."

FAQs

1. What is Jira used for?

Jira is used for:

• Bug Tracking

• Issue Tracking

• Project Management

• Agile Development (Scrum and Kanban)

2. What is an Issue in Jira?

An issue is the basic unit of work.

Examples include:

• Bug

• Story

• Task

• Epic

• Sub-task

• Improvement

• Change Request

• Spike

3. What is the difference between an Epic, Story, Bug, and Task?

• Epic – Large business objective.

• Story – User-facing feature.

• Bug – Software defect.

• Task – General or technical work.

4. What are the common Issue Types in Jira?

• Epic

• Story

• Task

• Bug

• Sub-task

Optional:

• Improvement

• Spike

• Custom Issue Types

5. What is a Project in Jira?

A collection of related:

• Issues

• Workflows

• Boards

• Users

• Permissions

• Settings

organized under a common goal.

6. What is a Workflow in Jira?

The lifecycle of an issue, consisting of statuses, transitions, and rules.

7. What is the Backlog in Jira?

A prioritized list of pending stories, tasks, and bugs waiting to be planned into future sprints.