Jira Full Notes PDF – Complete Notes with Examples
These notes explain the 9 most important Jira topics in simple language, with practical examples from a real-world-style e-commerce application. They are useful for beginners, experienced testers, and QA interview preparation.
1. What is Jira and how do QA teams use it?
Jira is a software tool used to manage tasks, report bugs, track defects, and monitor development and testing progress.
QA testers use Jira to record issues they find during testing and communicate them to developers.
Important Jira terms
Term | Meaning |
|---|---|
Project | Workspace for an application |
Issue | A bug, task, story, or other work item |
Bug | A problem found in the application |
Assignee | Person responsible for the issue |
Reporter | Person who created the issue |
Status | Current stage of the issue |
Issue key | Unique ID, such as SHOP-101 |
Example:
You are testing an online shopping website and discover that clicking Add to Cart does not add a product to the cart.
- Open Jira.
- Open the relevant project.
- Create an issue with type Bug.
- Enter the problem description and reproduction steps.
- Attach a screenshot or video.
- Assign the bug to the appropriate developer.
The issue might be identified as
SHOP-101.Interview point: Jira helps QA teams report defects, track their status, collaborate with developers, and monitor testing progress.
2. Bug life cycle and defect reporting
What is the bug life cycle?
The bug life cycle is the sequence of stages a defect passes through from discovery until it is verified and closed.
New / Open
In Progress
Fixed / Resolved
Retesting
Closed
If the defect still exists, the tester reopens it or returns it to development.
The actual statuses depend on the Jira workflow configured by the organization.
What is defect reporting?
Defect reporting means documenting a problem so that another team member can understand and reproduce it.
A good bug report includes:
- Bug title
- Steps to reproduce
- Expected result
- Actual result
- Severity and priority
- Environment and build details
- Screenshot, video, or logs when relevant
Example:
Bug: Add to Cart button is not working
Issue type: Bug
Steps to reproduce
- Open the shopping website.
- Open a product page.
- Click Add to Cart.
Expected result: The product should be added to the shopping cart.
Actual result: The cart remains empty.
Environment: Chrome browser, QA environment.
Evidence: Attach a screenshot or screen recording.
Interview point: A good defect report is clear, reproducible, and supported by evidence.
3. Severity vs priority
These are two different concepts used when reporting and managing defects.
- Severity: How seriously the defect affects the application’s functionality.
- Priority: How urgently the defect should be fixed.
Example | Severity | Priority |
|---|---|---|
Payment fails for all customers | High | High |
Company logo is incorrect before launch | Low | High |
Rarely used feature fails in a non-critical scenario | High | Low |
Minor spacing issue on a secondary page | Low | Low |
These are illustrative combinations. The correct values depend on business impact, affected users, and release requirements.
Real-time example:
A payment failure prevents customers from completing purchases. It has high severity because a critical function is broken, and high priority because the business needs it fixed urgently.
A small alignment issue on a rarely visited page may have low severity and low priority.
Interview question: Can a low-severity bug have high priority?
Answer: Yes. For example, an incorrect company logo on the homepage may not affect functionality, but it might need urgent correction before a major launch.
4. Jira workflows and status transitions
What is a Jira workflow?
A workflow defines the stages an issue can move through and the permitted transitions between those stages.
For example, a defect might follow this workflow:
- Open
- In Progress
- Resolved
- Closed
If the fix fails during testing, the tester may reopen the issue.
What is a status transition?
A status transition is an action that moves an issue from one status to another.
Example:
A developer finishes fixing a login bug and moves it from In Progress to Resolved. The QA tester retests the login functionality.
- If login works correctly, the tester moves the bug to Closed.
- If login still fails, the tester reopens the bug or moves it back to development, according to the team’s workflow.
Important distinction:
- Status = current stage.
- Transition = action that changes the stage.
- Resolution = outcome recorded when an issue is resolved, depending on the project’s configuration.
Interview point: A defect should be closed only after the fix has been verified according to the team’s process.
5. Agile, Scrum, user stories, and sprints
1. Agile
-Agile is an approach to software development in which teams deliver software in small increments and improve it through feedback.
2.Scrum
Scrum is an Agile framework that organizes work into short, fixed periods called sprints.
Important terms
Term | Meaning | Example |
|---|---|---|
Epic | Large feature or goal | Online shopping |
User Story | Requirement from the user’s perspective | Customer login |
Task | A specific unit of work | Test login validation |
Sprint | Fixed development period | Two-week sprint |
Backlog | List of pending work | Login, search, cart |
Acceptance Criteria | Conditions a feature must satisfy | Invalid login displays an error |
Example of a user story
“As a customer, I want to log in using my email and password so that I can access my account.”
Acceptance criteria:
- Valid credentials allow the user to log in.
- Invalid credentials display an appropriate error message.
- Empty fields display validation messages.
The tester uses these criteria to design test scenarios, execute tests, and report defects in Jira.
What does QA do during a sprint?
- Understand the user story.
- Review acceptance criteria.
- Prepare test scenarios.
- Execute tests when the feature is available.
- Report defects in Jira.
- Retest fixes and perform regression testing.
- Share testing progress during daily stand-ups.
Interview point: QA testing is not limited to the end of a sprint. Testers participate throughout the development process.
6. Basic JQL queries
JQL stands for Jira Query Language. It allows testers to search and filter issues using specific conditions.
Assume your project key is
SHOP.Requirement | JQL query |
|---|---|
Find all bugs | project = SHOP AND issuetype = Bug |
Find unresolved bugs | project = SHOP AND issuetype = Bug AND resolution IS EMPTY |
Find high-priority bugs | project = SHOP AND priority = High |
Find bugs in progress | project = SHOP AND issuetype = Bug AND status = "In Progress" |
Find issues assigned to you | assignee = currentUser() |
Find recently updated issues | project = SHOP AND updated >= -7d ORDER BY updated DESC |
Example explained
project = SHOP AND issuetype = Bug AND resolution IS EMPTYThis query finds bugs in the
SHOP project that have no recorded resolution.Why do testers use JQL?
Suppose a QA lead asks for all unresolved bugs before a release. Instead of opening each issue individually, the tester can run a JQL query to find them quickly.
Note that JQL searches depend on your permissions and configured field values.
7. Test execution and linking defects
What is test execution?
Test execution means running test cases against the application and recording whether the actual results match the expected results.
Common outcomes are:
- Passed: Actual result matches the expected result.
- Failed: Actual result does not match the expected result.
- Blocked: Testing cannot continue because of a dependency or another issue.
Example: Login testing
Test case | Expected result | Actual result | Status |
|---|---|---|---|
Valid credentials | Login successful | Login successful | Passed |
Invalid password | Error message displayed | Error message displayed | Passed |
Empty password | Validation message displayed | No validation message | Failed |
If the third test fails because the application is behaving incorrectly, the tester creates a bug in Jira.
What is linking a defect?
Linking connects related Jira issues so the team can understand their relationship.
For example:
- User Story:
SHOP-100— Customer login. - Bug:
SHOP-105— Empty password does not show a validation message. - QA Task:
SHOP-110— Execute login test cases.
The tester links the bug to the login story and, where appropriate, to the QA task or test case.
This helps the team identify which requirement is affected by a defect.
Important: Jira’s standard issue tracking supports issue links, but dedicated test case repositories and detailed test execution usually require a test management app such as Xray or Zephyr.
8. Bug tracking and QA reporting
What is bug tracking?
Bug tracking means monitoring defects from the time they are reported until they are resolved, retested, and closed.
Testers monitor:
- Newly created bugs
- Open and unresolved bugs
- Bugs assigned to developers
- Fixed bugs awaiting retesting
- Reopened bugs
- Closed bugs
What is QA reporting?
QA reporting communicates testing progress and product quality to the team or management.
A basic QA report might include:
Metric | Example |
|---|---|
Total bugs reported | 40 |
Closed bugs | 25 |
Open bugs | 10 |
Reopened bugs | 3 |
Bugs awaiting retesting | 2 |
These are illustrative numbers. Actual counts should come from the project’s Jira data and agreed reporting definitions.
Example:
Before a release, the QA lead finds that 10 bugs remain open, including 2 critical payment defects. The team reviews those defects before deciding whether the application is ready for release.
Interview point: QA reports help teams understand defect status, testing progress, and potential release risks.
9. Complete real-time testing scenario
Let’s consider an e-commerce website where a customer can log in, add products to a cart, and make payments.
Step 1: Understand the requirement
User story: “As a customer, I want to add a product to my cart so that I can purchase it later.”
Acceptance criterion: Clicking Add to Cart should add the selected product to the cart.
Step 2: Execute the test
Open the product page, select a product, and click Add to Cart. Verify that the cart displays the correct product and quantity.
Step 3: Report the defect
Suppose the cart remains empty. Create a Jira bug with reproduction steps, expected and actual results, environment details, and evidence.
Step 4: Developer fixes the bug
Assign the bug to the developer. The developer investigates the issue, fixes it, and updates the Jira status according to the workflow.
Step 5: Retest and perform regression testing
Verify that the product is added correctly. Also check that changing quantity, removing products, and viewing the cart still work.
Step 6: Close the bug and report results
If the fix works, close the defect according to the workflow. Update the QA report and communicate the final testing status.
Practice interview question
Question: You reported a bug in Jira, but the developer marked it as fixed. During retesting, the bug still exists. What will you do?
Answer: I will reproduce the issue, verify the environment and build, collect updated evidence, and add a comment explaining why the issue persists. I will reopen the bug or return it to development according to the team’s workflow, then retest it after the next fix.