📋 Jira

Learn Jira as a QA engineer: bug report anatomy, issue types, workflows, JQL queries, Scrum and Kanban boards, test management and REST API automation.

Jira is where a QA engineer spends the day: bugs are recorded, prioritized, verified and measured here. On this page you will follow a bug's whole journey from record to quality metric -- writing a strong report, workflows and permissions, querying with JQL, Scrum and Kanban boards, test management add-ons, CI/CD integration and automation through the REST API -- all on one running example, ShopQA.

What you can learn on this page

  • 🏠 What is Jira? — Think of Jira as a hospital patient-record system. Every complaint that walks in opens a file: who brought it, with which symptom, which tests were run, which doctor did what and when, was it discharged, did it come back for a check-up. Doctors also tell each
  • ⚙️ Setup & First Project — Opening a new Jira project is like choosing the lock system of a laboratory. There are two options: keep the key inside the room (team-managed -- the team configures its own fields, statuses and permissions) or use a central key cabinet (company-managed -- sch
  • 🧩 Issue Types & Hierarchy — Picture a construction project: the floor plan (Epic) describes a whole goal, each apartment (Story) is a deliverable piece, and the individual jobs inside it (Sub-task) are the steps that finish that piece. A Bug arrives from outside this hierarchy: it is dam
  • 🐞 The Art of Bug Reporting — A good bug report is like an accident report. The person writing it stands alone at the scene; the adjuster who reads it will never go there. That is why the report does not say "a car crashed" -- it says which junction, which lane, which weather, wh
  • 🔄 Workflows & Statuses — A workflow is like the sequence of gates at an airport: check-in, security, passport, boarding. Passing each gate requires permission and the order cannot be skipped -- you do not board before passport control. In Jira every status is a waiting lounge and ever
  • 🔍 JQL: Jira Query Language — JQL is like a library card catalogue: instead of walking the shelves you ask for "books published after 2019, by this author, on this subject" and the library brings back only those. A board shows you the shelves; JQL gives you a list filtered by you
  • 📋 Scrum & Kanban Boards — Picture the order board of a restaurant kitchen: orders come in from the left, pass through prep stations and leave to service on the right. The number of burners is limited -- you can only boil four pots at once. That limit is not a flaw, it is the reality of
  • 🧪 Test Management: Xray & Zephyr — An aircraft keeps two separate logbooks: fault records (what broke, when, how it was cleared) and maintenance checklists (which check, before which flight, performed by whom). Both are mandatory and neither substitutes the other. Jira alone keeps the first boo

Frequently Asked Questions

What is Jira, in one sentence?

Jira is a work-tracking and project-management system where a team records, prioritizes and verifies bugs, requirements and work items under a permanent identity.

Is Jira free?

Jira Cloud offers a free plan for up to 10 users, enough for small teams and learning purposes. Larger teams and extra features (advanced reporting, permission schemes) require paid tiers.

What is the difference between Jira and Trello?

Trello is a general-purpose, simple Kanban board -- quick to set up but lacking software-development-specific structures like issue types, workflow conditions, or a traceability matrix. Jira is built for software teams: a bug/story/epic hierarchy, the JQL query language, and test management add-ons (Xray/Zephyr) support a much deeper engineering process.

Do I have to learn Jira as a QA engineer?

It is not mandatory, but it is the most widely used work-tracking tool in the industry -- many job listings ask for Jira experience. More importantly, learning Jira is not just learning a tool: this page also teaches tool-independent QA skills like bug reporting, traceability and quality metrics.

Is JQL hard to learn?

If you know SQL, JQL will feel familiar -- field, operator, value and ordering line up with the same logic. The steepest part of the learning curve is grasping that JQL is NOT a database language (it cannot JOIN); once you know that boundary, daily use settles in quickly.

Which should I learn, Jira Cloud or Jira Data Center?

Start with Jira Cloud -- the vast majority of accounts opened today are Cloud, and you can try it immediately with a free account. The core concepts (issue, workflow, JQL) are identical in both; only a few points differ when you move to Data Center, like the REST API address and the project type options.

What is most commonly asked about Jira in a QA interview?

What makes a bug report "good" (exact steps, expected vs. actual result, environment details), and how an issue moves from one workflow status to another. Follow-up questions usually cover writing a JQL query like "open bugs assigned to me" and how you would interpret a quality metric like the reopen rate.