If your team receives a lot of bug reports, you’ve probably noticed the same issue getting reported by multiple users, filling up your bug list with near-identical entries. Every duplicate needs to be read, triaged, and either closed or linked back to the original. It’s a lot of repetitive work.
Bug Grouping is Luciq’s way of handling that work for you. When a new bug report is received, Luciq reviews it and determines whether it’s a duplicate of a recent one. If it is, the report is automatically grouped under a single master report, so your team can see the full scope of the issue at a glance and act once, in one place.
Good to know: Bug Grouping works side-by-side with the existing Mark as Duplicate action. Manual grouping by your team continues to work exactly as it does today. Bug Grouping simply adds an automatic layer on top.
The bug list showing reports tagged as Auto grouped and Manually grouped, with the master report detail panel open on the right.
Why use Bug Grouping
Bug Grouping helps your team stay focused on the issues that matter, not on sorting through duplicates. It delivers three big benefits:
Less triage work. Duplicate reports are automatically detected and grouped, so your bug list stays clean, and your team spends less time reviewing duplicates.
A clearer picture of impact. When duplicates are grouped under a single master report, you can immediately see how many users are hitting the same issue and prioritize accordingly.
One action updates the whole group. Assigning, setting a status, or changing priority on the master report applies across all its duplicates.
How it works
When a new bug report comes in, Luciq compares it against recent reports and decides whether it belongs to an existing group or should stand on its own.
Semantic matching. Reports are compared based on the meaning of their content, not just exact wording, to find likely duplicates.
Group assignment. If a match is found, the new report is added to the group as a duplicate. If not, it remains as a single, ungrouped report.
Fast fallback. Grouping happens on the Luciq backend. If the automatic grouping doesn’t complete within 30 seconds, the report appears as an ungrouped report, so your workflow is never blocked.
What the grouping logic looks at
To decide if two reports belong together, Luciq focuses primarily on:
The semantic similarity of the report descriptions, and
The report category/type (for example, a Bug report won’t be grouped with a Question).
A couple of things to keep in mind:
Subcategory is not used in grouping.
Other attributes like screen name or app version are not part of the current grouping logic either.
What you’ll see in the dashboard
With Bug Grouping enabled, every bug report in your list will be one of three types:
Ungrouped report (Single): Not part of any group yet.
Manual group: Created by your team using the Mark as Duplicate action.
Automatic group: Detected and grouped automatically by Luciq.
Automatic group masters are visually distinguished from manual ones, so you always know which type you’re looking at.
Key terms
Master report: the parent report that represents the group’s canonical issue.
Duplicate report: a report (automatic or manual) that’s been marked as a duplicate of a master.
Ungrouped / Single report: a report that isn’t part of any group.
Automatic master report details
When you open an automatic master report, you’ll see an Automatic group master section at the top of the report that includes:
Group summary: a short description of the shared issue across all the duplicates in the group. It may take a short time to appear after grouping.
Grouping confidence: a confidence indicator for the grouping decision. Group-level confidence is based on the automatic duplicates in the group; manual duplicates don’t contribute to it.
Number of grouped reports: how many duplicates are in the group.
Show duplicates: a shortcut to view every duplicate in the group in a dedicated list.
The Automatic group master section showing the summary, confidence indicator, number of duplicates, and a Show duplicates link.
Automatic duplicate report details
When you open a report that was automatically marked as a duplicate, you’ll see a banner at the top letting you know, plus a shortcut to jump to its master.
A banner at the top of the report confirms it was automatically marked as a duplicate and provides a shortcut to open the master.
Actions and workflows
Automatic groups follow the same core workflow as manual duplicates. The most important principle to remember is master-first actions:
Update from the master. Changes to status, assignee, or priority on the master report propagate to all duplicates in the group.
Duplicates are restricted. You can’t apply master-level actions directly from a duplicate report; you’ll do it from the master instead.
Changing a group’s master or marking a report as a duplicate:
For an ungrouped/single report, you can mark it as a duplicate of an existing master.
For a master report, you can change it to another ungrouped report or to another master (in which case the two groups are merged).
For a duplicate report, you can unmark it to remove it from the group.
Filtering and bulk actions
Bug Grouping adds a new Report Groups filter to the dashboard, allowing you to quickly narrow your bug list to what you need. You can filter by:
Ungrouped reports
Automatic → Masters / Duplicates
Manual → Masters / Duplicates
Bulk actions are intentionally limited to prevent accidental changes across duplicates. If your current filter selection includes duplicates or doesn’t target masters appropriately, bulk actions will be disabled, and you’ll see a tooltip explaining why.
A tooltip warns when bulk actions aren’t available. Unselect duplicates from the list using the Report Groups filter to re-enable them.
Tags for master and duplicate reports
To help you distinguish master and duplicate reports consistently, including in the integrations you forward reports to, Luciq automatically tags grouped reports at creation time:
Master reports are tagged with Luciq_Master_report.
Duplicate reports are tagged with Luciq_Duplicate_report.
These tags can also show up in your third-party tools (like Jira) that support two-way tag sync, so you can tell at a glance which is which even outside the Luciq dashboard.
The Tags section of a bug report, with the Master_report tag applied on the right-hand panel.
Note: If Tags Sync is disabled in your 3rd-party integration, master report tags may not appear in certain tracking views when reports are forwarded automatically.
Alerts and rules for grouped reports
If you use Alerts & Rules to automate your workflows, Bug Grouping gives you more precise control over which reports trigger them. You can target:
Master & Ungrouped reports: the recommended option for most teams, as it avoids firing alerts every time a duplicate is added to an existing group.
Any report type: including duplicates, which is useful if you want to track every incoming report.
You can also build rules around the Luciq_Master_report and Luciq_Duplicate_report tags to trigger automations when a report becomes a master or when it’s marked as a duplicate.
What to expect (and what not to expect)
What to expect:
Faster triage thanks to automatic duplicate detection.
A clear visual distinction between manual and automatic groups.
A master-first workflow: a single action on the master updates the entire group.
What not to expect (yet):
New reports won’t be automatically grouped into existing manual groups.
Perfect grouping in every case, you can always adjust groups manually when needed.
Duplicates grouped into closed or resolved issues. Once a group is closed, it stops collecting new duplicates.
Enabling Bug Grouping
Bug Grouping is available on request. To turn it on for your account, contact our support team or your Customer Success Manager.
Note: Once enabled, Bug Grouping is applied only to reports received after the feature is turned on. It is not applied retroactively to older bug reports.