How to Use This List

These are the Jira interview questions that QA Engineers, Manual Testers, and Automation Testers are most commonly asked. The questions are grouped by topic for quick revision, and each answer provides a concise explanation. For complete concepts, examples, and practical demonstrations, continue with the Complete Jira Guide.

Jira Fundamentals (Q1–Q5)

1. What is Jira and why do testers use it?

Jira is an Atlassian project management and issue-tracking tool. Testers use it to log defects, manage Agile sprints, track testing activities, and collaborate with development teams.

Learn More: Jira Fundamentals

Advertisement

2. What are the issue types in Jira?

Common issue types include Epic, Story, Task, Sub-task, and Bug. Organizations can also create custom issue types based on their project requirements.

Learn More: Jira Fundamentals

3. What's the difference between an Epic, a Story, and a Task?

  • Epic: A large feature that may span multiple sprints.
  • Story: A user requirement or business functionality.
  • Task: A unit of work that needs to be completed.

Learn More: Jira Fundamentals

4. What's the difference between a Bug and a Sub-task?

A Bug represents a software defect, while a Sub-task is a smaller work item created under a parent issue.

Learn More: Working with Jira Issues

5. What is a Workflow in Jira?

A workflow defines the statuses and transitions that an issue moves through during its lifecycle, such as To Do → In Progress → Done.

Learn More: Jira Administration

Defects & Issues (Q6–Q10) 

6. How do you log a bug in Jira?

Create a defect with a summary, description, reproduction steps, expected and actual results, severity, priority, environment details, attachments, and assignee.

Learn More: Working with Jira Issues

7. What is the Defect Life Cycle in Jira?

A typical defect lifecycle is:

New → Assigned → Open → Fixed → Retest → Closed

Alternative statuses may include Reopened, Deferred, or Rejected.

Learn More: Working with Jira Issues

8. What's the difference between Severity and Priority?

  • Severity: Technical impact of the defect.
  • Priority: Business urgency of fixing the defect.

Learn More: Severity vs Priority

9. What is Issue Linking used for?

Issue Linking connects related issues using relationships such as Blocks, Is Blocked By, Duplicates, and Relates To, improving traceability.

Learn More: Fields & Links

10. What's the difference between Resolution and Status?

Status indicates where an issue currently is in the workflow, while Resolution explains how the issue was completed, such as Fixed, Won't Fix, Duplicate, or Cannot Reproduce.

Learn More: Fields & Links

Agile Boards & Sprints (Q11–Q14)

11. What's the difference between a Scrum Board and a Kanban Board?

A Scrum Board uses fixed-length sprints and a sprint backlog, while a Kanban Board supports continuous work with Work-in-Progress (WIP) limits.

Learn More: Boards & Sprints

12. What is the difference between a Sprint Backlog and a Product Backlog?

The Product Backlog contains all pending work for the product, whereas the Sprint Backlog includes only the items selected for the current sprint.

Learn More: Boards & Sprints

13. What is a Burndown Chart?

A Burndown Chart shows the remaining work during a sprint and helps the team track progress toward completing sprint goals.

Learn More: Boards & Sprints

14. What are Story Points?

Story Points measure the relative effort, complexity, and uncertainty of user stories. They estimate work comparatively rather than in hours.

Learn More: Boards & Sprints

JQL & Reporting (Q15–Q17) 

15. What is JQL?

JQL (Jira Query Language) is used to search and filter Jira issues.

Example:

project = QA
AND status = Open
AND assignee = currentUser()

Learn More: JQL & Dashboards

16. Give a useful JQL query for a tester.

project = ABC
AND issuetype = Bug
AND status != Closed
AND priority = High
ORDER BY created DESC

This query returns all open high-priority bugs ordered by creation date.

Learn More: JQL & Dashboards

17. What are Filters and Dashboards used for?

Filters save JQL queries, while Dashboards display real-time project metrics such as defects, sprint progress, and testing status using dashboard gadgets.

Learn More: JQL & Dashboards

Test Management & Integrations (Q18–Q20)

18. How do you manage test cases in Jira?

Test cases are typically managed using plugins such as Zephyr or Xray, allowing teams to create test cases, test cycles, executions, and traceability links.

Learn More: Test Management

19. How does Jira integrate with automation?

Jira integrates with tools such as Jenkins, Git, Selenium, and test management platforms to connect automated test results, builds, and defects for complete traceability.

Learn More: Integrations

20. How do you handle a defect that the developer rejects as "Not a Bug"?

Verify the requirement or acceptance criteria, reproduce the issue, attach supporting evidence such as screenshots and logs, and involve the Business Analyst or Product Owner if the disagreement continues.

Learn More: Scenario-Based Jira

Next Steps