/
A practical approach to tracking long-running and reopened bugs in JIRA
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html' is unknown.

A practical approach to tracking long-running and reopened bugs in JIRA

In most Agile projects, bug handling follows a simple process. Tester raises a bug in JIRA, assigns it to the developer, and waits for the fix.

This process works, but during busy sprints teams often face tracking problems.

Some bugs remain open for many days.

Some bugs get reopened multiple times.

Some bugs are blocked due to deployment or dependency issues, but the reason is not clearly visible.

As a result, testers, developers, and managers spend a lot of time following up manually.

From my experience, the issue is not always the bug itself. The real problem is lack of visibility.

For example:

  • Which bugs are taking too long?

  • Which bugs are repeatedly reopening?

  • Which bugs are blocked?

  • Which bugs need urgent attention?

Normally teams need to open multiple tickets manually to understand this information. During sprint pressure, this becomes difficult.

One improvement I found useful is creating a simple Bug Ageing and Reopened Bug Tracking Framework using JIRA dashboards, filters, labels, and automation rules.

The idea is simple:
instead of waiting until sprint end, make delayed bugs visible earlier.

For example:

  • if a bug stays open for more than 3 days, it should appear in an “Ageing Bugs” dashboard

  • if a bug gets reopened multiple times, it should appear in a “Repeated Issues” dashboard

  • if a bug is blocked, blocker reason should be visible clearly

This helps the team quickly identify where delays are happening.

Simple Workflow

Below is a simple flow showing how ageing bugs and reopened bugs can be tracked using JIRA dashboards and automation.

Simple Workflow.png

 

Why This Helps

 

Role

Key Benefits

Business Impact

Role

Key Benefits

Business Impact

Developers

Better visibility of pending bugs, easier prioritisation, clear ownership

Faster resolution

Testers

Easy identification of retest and blocked bugs

Reduced manual follow-up

Managers / Scrum Masters

Visibility of bottlenecks, sprint tracking, reporting

Better decision making

 

Useful Dashboard Sections

The dashboard can include:

Dashboard Section

Example

Dashboard Section

Example

Ageing Bugs

Open for more than 3 days

Reopened Bugs

Defects reopened after QA retesting

Blocked Bugs

Waiting on dependencies or environments

Pending Retest

Ready for QA validation

Bugs by Developer

Ownership and workload tracking

 

Example in Practice

Imagine a bug related to a payment gateway integration remains in In Progress status for five days due to an external API dependency.

Because the bug appears automatically in the Ageing Bugs dashboard after three days, the Scrum Master can quickly identify the delay during the daily stand-up. The team can then escalate the dependency issue before it impacts sprint delivery.

Similarly, if a defect is reopened multiple times after testing, it can be highlighted in a Reopened Bugs dashboard, helping the team investigate whether additional root cause analysis is required.

These dashboards provide early visibility into potential risks, allowing teams to take action before issues affect release timelines.

Example JQL Queries

Bugs Open for More Than 3 Days

project = ABC AND issuetype = Bug AND status != Done AND created <= -3d

Reopened Bugs

project = ABC AND issuetype = Bug AND status = Reopened

Blocked Bugs

project = ABC AND labels = Blocked

These filters can easily be added into JIRA dashboards using gadgets like:

  • Filter Results

  • Pie Chart

  • Created vs Resolved Chart

Using Automation for Better Tracking

Another useful improvement can be using simple JIRA automation rules.

For example:

  • if a bug stays in the same status for more than 3 days, JIRA can automatically send reminder notification

  • labels like “Needs Attention” can be added automatically

  • Scrum Master or lead can receive notification for long pending bugs

This reduces manual follow-up effort.

This can be configured from:

Project Settings → Automation → Create Rule

Simple setup:

  • Trigger → Scheduled Rule

  • Condition → Bug still “In Progress”

  • Action → Send reminder or add label

Reopened Bug Automation

Automation can also help with reopened bugs.

If the same bug gets reopened multiple times, JIRA can automatically:

  • add label like “Repeated Issue”

  • notify developer lead

  • highlight ticket in dashboard

This helps the team identify whether proper root cause analysis was done before closing the bug.

Blocked Bug Tracking

Another useful improvement is for blocked bugs.

If a developer changes ticket status to “Blocked”, JIRA can make blocker reason mandatory.

For example:

  • Waiting for deployment

  • Environment issue

  • API dependency pending

  • Waiting for business confirmation

This can be implemented using:

  • dropdown fields

  • labels

  • workflow validation

This improves visibility because anyone opening the ticket can immediately understand why work is delayed.

Conclusion

Effective bug management is not just about logging defects in JIRA—it is about ensuring issues remain visible throughout their lifecycle.

By combining dashboards, JQL filters, labels, and automation rules, teams can proactively identify ageing, blocked, and repeatedly reopened bugs before they impact sprint delivery.

These improvements require minimal effort to implement but can significantly enhance transparency, accountability, and collaboration across Agile teams. As a result, developers, testers, and Scrum Masters can focus on resolving critical issues earlier and deliver higher-quality outcomes with greater predictability.

References