Bug Grouping | Alerts & Rules

This page provides alert and rule recommendations if you have Bug Grouping enabled.

Overview

If you have Bug Grouping enabled, you can choose which report types to alert on or automate with rules. You can set alerts or rules for:

  • Master & Ungrouped reports: the parent report and any report that is not part of any group.

  • Duplicate report: a report automatically or manually marked as a duplicate of a master.


How it works

Main Approach

Start by choosing a trigger. You can target either Any report type or Master & Ungrouped reports.

To trigger on all reports (masters, singles, and duplicates), choose Any bug is reported. It triggers whenever you receive any bug report.

If you only want Master & Ungrouped/Single reports (recommended), choose Not a duplicate bug is reported. This reduces noise from alerts when a duplicate report is received.

Another Approach | Utilize report tags

  • By default, when a report becomes a master report, a new "Luciq_Master_report" tag is added to it.

  • The same applies to duplicate reports. When a duplicate bug is reported, it gets a new "Luciq_Duplicate_report" tag.

  • You can use these tags to trigger a rule when:

    • A bug report becomes a group master.

    • A bug report is marked as a duplicate of an existing report.

Setting a rule for master reports
Setting a rule for duplicate reports
circle-exclamation

Noise Alert

circle-info

Why are Master & Duplicate reports tagged?

For 3rd-party integration tools that support 2-way tag sync (for example, Jira), these tags can show up in those tools. They help you identify the report type outside the Luciq dashboard.


Good to know

  • By default, our Triage Agent adds a comment in the Activity & Comments section when a new duplicate report is added to a master report.

  • This comment is then be shown in Jira (or other integrations that support syncing of comments) to update you on the volume of duplicate reports received.

Triage Agent's comment on Luciq's dashboard
Triage Agent's comment inside the Jira ticket
circle-info

Note on comments syncing

Make sure you enable the Comment One-way Sync from Luciq to Jira for the comments to reflect on Jira.

Last updated