Jira Interview Questions

Advertisement

Jira Fundamentals (Q1–Q5)

These are the Jira questions QA engineers, manual testers and automation testers are asked most often, grouped by topic with a clear answer for each — plus five bonus questions interviewers use to check real, hands-on experience. For the complete picture, see The Complete Jira for Testers Guide.

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

Jira is Atlassian's issue-tracking and Agile project management tool. Testers use it to log and track defects, follow sprint work, see which stories are ready for testing, manage test cases (with Xray or Zephyr) and report quality through filters and dashboards.

Learn more: Jira Fundamentals

2. What are the issue types in Jira?

The standard types are Epic, Story, Task, Sub-task and Bug. Organizations can add custom types, and test management apps add types such as Test, Test Set and Test Execution.

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

  • Epic — a large feature that spans several sprints, such as "Checkout redesign".
  • Story — a user-facing requirement with acceptance criteria, such as "Apply a coupon at checkout".
  • Task — a piece of work that isn't a user story, such as "Set up the test environment".

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

A Bug is a defect — something that doesn't work as expected. A Sub-task is a smaller piece of work under a parent issue, such as "Write automation for SHOP-214". A bug found while testing a story is usually logged as a Bug and linked to that story.

Learn more: Working With Jira Issues

5. What is a workflow?

The set of statuses an issue moves through and the transitions allowed between them — for example To Do → In Progress → In Review → Done. Admins can customize workflows per project and issue type.

Learn more: Jira Administration

Defects & Issues (Q6–Q10)

6. How do you log a bug in Jira?

Search for duplicates first, then create a Bug with a clear summary (where + what's wrong), environment and build, steps to reproduce, expected and actual results, severity and priority, attachments (screenshots, recordings, logs), component and affected version — and link it to the story it relates to.

Learn more: Defect Management in Jira

7. What is the defect life cycle in Jira?

A typical flow:

New → Assigned/Open → In Progress → Fixed → Ready for Retest → Closed

with Reopened when a retest fails. Other outcomes include Rejected, Duplicate, Deferred and Cannot Reproduce. The exact names depend on your company's workflow.

Learn more: Defect Bug Management

8. What's the difference between severity and priority?

Severity is the technical impact of the defect; priority is how urgently the business wants it fixed. They're independent — a wrong company logo on the home page is low severity but high priority.

Learn more: Severity vs Priority

9. What is issue linking used for?

Connecting related issues with relationships such as blocks / is blocked by, duplicates, relates to and clones. For testers it gives traceability:

story → test → bug

Learn more: Fields, Links & Resolution

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

Status is where the issue is in the workflow (In Progress, Done). Resolution records how it ended — Fixed, Won't Fix, Duplicate, Cannot Reproduce.

An issue with an empty resolution is "Unresolved", which is why JQL filters often use:

resolution = Unresolved

Agile Boards & Sprints (Q11–Q14)

11. Scrum board vs Kanban board?

A Scrum board works in fixed-length sprints planned from a backlog. A Kanban board shows a continuous flow of work, usually with work-in-progress (WIP) limits on columns.

Learn more: Boards, Sprints & Agile

12. Product backlog vs sprint backlog?

The product backlog holds all prioritized work for the product. The sprint backlog holds only the items the team committed to for the current sprint.

13. What is a burndown chart?

A chart of remaining work against time in a sprint. The ideal line slopes down to zero; a flat line means work isn't being completed, and upward jumps usually mean scope was added mid-sprint.

14. What are story points?

A relative estimate of a story's effort, complexity and uncertainty, compared with other stories rather than measured in hours — often estimated with planning poker. Testing effort should be included in the estimate.

JQL & Reporting (Q15–Q17)

15. What is JQL?

Jira Query Language — a search language for filtering issues by fields, functions and history:

project = QA AND assignee = currentUser() AND resolution = Unresolved

Learn more: Search, Filters, JQL & Dashboards

16. Give some useful JQL queries for a tester.

Open high-priority bugs, newest first:

project = ABC AND issuetype = Bug AND priority in (Highest, High) AND resolution = Unresolved ORDER BY created DESC

Bugs in the current sprint:

project = ABC AND issuetype = Bug AND sprint in openSprints()

Bugs reopened this week:

project = ABC AND issuetype = Bug AND status CHANGED TO "Reopened" DURING (startOfWeek(), now())

More: Jira & JQL Cheat Sheet

17. What are filters and dashboards used for?

A filter is a saved JQL query you can share, subscribe to or put on a board. A dashboard displays filters through gadgets — open bugs by priority, created vs resolved, sprint progress — to show quality at a glance.

Test Management & Integrations (Q18–Q20)

18. How do you manage test cases in Jira?

Jira has no built-in test cases, so teams add an app such as Xray or Zephyr for test cases, test cycles and executions, linked to stories and bugs for coverage and traceability.

Learn more: Test Management with Zephyr & Xray

19. How does Jira integrate with automation?

Through Git (issue keys in branch names and commit messages link code to issues), CI tools such as Jenkins (builds and deployments linked to issues), test management apps that import automated results, and Jira's REST API for creating or updating issues automatically.

Learn more: Jira Integrations

20. A developer rejects your bug as "Not a Bug". What do you do?

Re-check the requirement and acceptance criteria, reproduce the issue with clear evidence (steps, screenshots, recording, logs), and discuss it factually.

If the requirement itself is unclear, involve the business analyst or product owner to decide — and record the decision in the ticket.

Learn more: Scenario-Based Jira Questions

Bonus: 5 Questions That Test Hands-On Experience

Affects Version vs Fix Version?

Affects Version is the release where the bug was found; Fix Version is the release where it will be (or was) fixed. Release notes and regression scope are built from Fix Version.

Component vs Label?

Components are admin-defined modules of a project (Checkout, Payments), often with a default assignee. Labels are free-form tags anyone can add (regression, mobile). Components are more consistent for reporting.

Cloning creates a copy of an issue — useful when the same bug appears in another release or project. Linking connects two existing issues without copying anything.

How Do You Update Many Issues at Once?

Run a JQL search, then use Bulk Change from the results to transition, edit fields, move or delete multiple issues — permissions allowing.

How Do You Report Testing Status to the Team?

With a dashboard built from saved filters:

  • Open bugs by severity and priority

  • Bugs ready for retest

  • Created vs resolved in the sprint

  • Stories still waiting for testing

Along with the dashboard, provide a short written summary of risks.

From Real Projects

Jira has been my defect-tracking tool throughout my testing career, with TestRail for test execution. Preparing bug reports, retesting fixes and taking part in sprint planning, reviews and retrospectives all meant working in Jira every day. Learn the workflow your team uses, and keep every bug linked to the story it affects. On Canolog, every department — sales, inventory, finance, service and parts — connects to the others, so a change in one module had to be checked in the flows that depend on it. Be ready to walk through a bug's full life cycle in your team's Jira workflow, status by status.

📖 Related tutorials

📚 Official documentation: Jira Cloud documentation (Atlassian)

FAQs

What Jira Topics Are Asked Most in QA Interviews?

Issue types, the defect life cycle, severity vs priority, Scrum boards and sprints, JQL, and test management with Xray or Zephyr.

Do I Need to Write JQL in an Interview?

Often, yes — a simple query such as open bugs assigned to you, or bugs in the current sprint. Practice with the queries above.

Resolution vs Status — What's the Difference?

Status is the current workflow step; resolution records how the issue was completed.

How Can I Practice?

Create a free Jira Cloud site, log sample bugs, run a sprint and build a dashboard — then take a timed round in the Jira Interview Simulator.

Next Steps