Introduction
JIRA is one of the most widely used project management and defect tracking tools in Agile projects. Manual testers use JIRA to log, track, and manage defects efficiently.
What is JIRA?
JIRA is an issue tracking and project management tool developed by Atlassian. It supports Agile methodologies like Scrum and Kanban.
- Defect tracking
- Backlog management
- Sprint planning
- Workflow customization
- Reporting and dashboards
How JIRA is Used in Manual Testing
- Log defects during test execution
- Assign bugs to developers
- Track defect status
- Link bugs to user stories
- Generate defect reports
JIRA Defect Workflow
- New
- Assigned
- In Progress
- Fixed
- Retest
- Closed
- Reopened (if issue persists)
Important Fields in JIRA Bug
- Summary
- Description
- Steps to Reproduce
- Expected Result
- Actual Result
- Priority
- Severity
- Attachments (screenshots/logs)
JIRA Dashboard & Reports
- Defect count by status
- Open vs Closed defects chart
- Sprint burndown chart
- Defect trend analysis
Dashboards help stakeholders track sprint health and product quality.
Real-Time Project Example
Example: Banking Application
- Tester executes fund transfer test case.
- Finds incorrect error message.
- Logs defect in JIRA with steps and screenshot.
- Developer fixes issue and updates status.
- Tester retests and closes defect.
Interview Questions
What is JIRA used for in manual testing?
JIRA is used for defect tracking, sprint management and reporting.
Explain JIRA defect lifecycle.
New → Assigned → In Progress → Fixed → Retest → Closed.
What details are mandatory while logging a bug in JIRA?
Summary, steps to reproduce, expected result, actual result, priority and severity.
Frequently Asked Questions
Is JIRA only for Agile?
No, but it is widely used in Agile projects.
Can testers customize workflows in JIRA?
Yes, depending on project configuration and permissions.