Logging a Defect in Jira

Step-by-Step Approach

Reproduce the Defect

Before logging the issue:

  • Reproduce the defect.
  • Verify it is consistent.
  • Note the exact steps.
  • Record test data.
  • Record environment details.

Collect Evidence

Gather:

  • Screenshots
  • Screen recordings
  • Logs
  • API Responses

Also capture:

Advertisement
  • Browser
  • Device
  • Operating System
  • Application Version

Open Jira and Fill the Required Fields

Complete:

  • Summary
  • Description
  • Steps to Reproduce
  • Expected Result
  • Actual Result
  • Severity
  • Priority
  • Environment

Add Additional Information

Attach:

  • Screenshots
  • Videos
  • Logs
  • Build Number
  • Version
  • Related Links

Save and Communicate

Create the defect and notify the Developer or Team so work can begin immediately.

Bug Fields and Linking Test Cases

Standard Bug Fields

A defect should include:

  • Summary
  • Detailed Description
  • Steps to Reproduce
  • Expected Result
  • Actual Result
  • Severity
  • Priority
  • Environment
  • Build / Version
  • Attachments

Linking Test Cases to User Stories

  • Create or select the Test Case.
  • Link the Test Case to the Jira Story.
  • Use Jira or the Test Management plugin.
  • Track execution and results.

This provides complete traceability:

Requirement → Test Case → Defect

The Bug Workflow (Status Flow)

A typical Jira defect moves through the following stages.

Open / New

The defect has been logged.

Assigned / In Progress

The Developer has been assigned and begins investigation.

Fixed / Ready for Retest

The Developer completes the fix and hands it back to QA.

Retest / Verified

QA verifies the fix.

If successful:

  • Close the defect.

If unsuccessful:

  • Reopen the defect.

Reopen

The issue still exists after the attempted fix.

The defect is reassigned to the Developer.

Other Possible Statuses

  • Rejected
  • Not a Bug
  • Deferred
  • Won't Fix

Defect Aging and Triage

Defect Aging

Defect aging is the amount of time a defect remains unresolved after it has been logged.

Long-aging defects can delay releases and become project bottlenecks.

Monitor aging using:

Escalate defects that exceed the agreed aging threshold.

Defect Triage Meetings

Before the Meeting

Review:

  • Open defects
  • Severity
  • Priority
  • Module
  • Assignee

During the Meeting

Discuss with:

  • Developers
  • QA Lead
  • Product Owner

Decide:

  • Severity
  • Priority
  • Fix timeline

After the Meeting

Update:

  • Status
  • Assignee
  • Priority
  • Comments

Severity vs Priority: Scenario Examples

Scenario Severity Priority Why
Login not working High High User blocked from app
Misspelled label on About page Low Low Cosmetic
Wrong total in billing High High Business loss
Logo missing Medium Low Branding issue
App crash on Save High High System failure
Incorrect tooltip text Low Low Minor
Contact form not submitting High High Core functionality
Font mismatch Low Medium UI-only
Email confirmation not sent Medium High Business impact

Key Learning

Severity measures technical impact.

Priority measures business urgency.

They are assigned independently.

Examples:

  • Logo missing
    • Medium Severity
    • Low Priority
  • Email confirmation not sent
    • Medium Severity
    • High Priority

Managing Priorities During Release & Bug Reports

Managing Defect Priorities During Release

Prioritize defects that:

  • Block critical business functionality.
  • Affect end users.
  • Impact production.

Low-impact defects can be deferred after discussion with the Product Owner.

Bug Summary Reports

Use Jira:

  • Filters
  • Dashboards

Summarize defects by:

  • Status
  • Severity
  • Priority
  • Module
  • Aging

These reports help stakeholders evaluate release readiness.

Team & Client Communication

Communicating Critical Issues to Management

Inform management immediately.

Keep communication:

  • Clear
  • Concise
  • Fact-based

Include:

  • Issue summary.
  • Business impact.
  • Functional impact.
  • Customer impact.
  • Urgency.

Handling Client-Reported Bugs

  • Listen carefully.
  • Acknowledge the concern.
  • Make the client feel heard.

Collect:

  • Steps to reproduce.
  • Screenshots.
  • Environment details.
  • Error messages.

Then begin investigation.

Other Communication Scenarios

Always:

  • Handle conflicts professionally.
  • Resolve Developer disagreements using evidence.
  • Clarify ambiguous requirements with the BA or Product Owner.
  • Communicate testing status and risks clearly.
  • Raise blockers early with business impact and dependency information.

FAQs

How Do You Log a Defect in Jira?

Reproduce the issue, collect supporting evidence, complete all required Jira fields, attach screenshots and logs, and notify the team.

What Is the Jira Bug Workflow?

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

If the issue still exists:

Reopen.

Other possible statuses include:

  • Rejected
  • Deferred
  • Won't Fix

What Is Defect Aging?

Defect aging measures how long a defect remains unresolved.

It is monitored using Jira Dashboards and escalated when it exceeds the project's aging threshold.

What's the Difference Between Severity and Priority?

Severity measures technical impact.

Priority measures business urgency.

Both are assigned independently.

How Do You Handle a Defect Triage Meeting?

Review all open defects beforehand, discuss severity and priority with Developers, QA Leads, and Product Owners, then update Jira with the agreed decisions.

How Do You Communicate a Critical Issue to Management?

Communicate immediately.

Clearly explain:

  • The issue.
  • Business impact.
  • Urgency.
  • Risks.

How Do You Handle a Client-Reported Bug?

Acknowledge the issue respectfully, gather complete reproduction details, investigate the problem, and provide regular updates.