Q1 of 14 · JIRA
What is JIRA and how do QA engineers use it day to day?
Short answer
Short answer: JIRA is a project-tracking tool by Atlassian used to create, assign, prioritise, and track issues (bugs, stories, tasks). QA engineers use it to file bugs, track test coverage, manage test cycles (via Xray or Zephyr), and monitor what's ready to test in a sprint.
Detail
JIRA is the most common issue tracker in software teams. For QA engineers the daily workflow typically involves:
Filing bugs — creating Bug issues with reproduction steps, expected vs actual behaviour, environment details, severity, and attachments (screenshots, logs).
Checking sprint readiness — what's in the current sprint, which stories are in "Ready for QA" or "In Testing" status, and which have been deployed to the test environment.
Linking issues — connecting a bug to the story it was found in ("Found in"), or marking duplicates and dependencies between issues.
Tracking test coverage — if the team uses Xray or Zephyr, test cases and test cycles are managed inside JIRA, linking test results to the corresponding story or bug.
Writing and updating test cases — in test-management plugins, test cases are JIRA issue types that can be assigned to test plans and cycles with pass/fail results recorded per run.
Querying with JQL — filtering issues programmatically to find all open bugs in a component, or all stories completed in the last sprint, for reporting and retrospective prep.
Reporting — creating dashboards with gadgets that show open bug count by priority, sprint velocity, bug age, or test-cycle completion percentage.