How to stop duplicate bug reports turning into duplicate tickets

Keep one parent ticket per root cause, link every report to it, reply to each person, and work within what Apple and Google allow in review replies.

Thinkiyo team··12 min read

Keep one parent ticket for each root cause and link every report to it. Count the reports on that ticket and let the count drive priority. Then reply to each person individually, on the channel they used, and tell them when it is fixed. Merging tickets is the easy part. The hard part is keeping the list of people you owe an answer, and writing a store reply inside the limits Apple and Google set.

How merging should work

Engineering teams solved this long ago, and the conventions carry over to support.

In Google's Issue Tracker, marking an issue as a duplicate closes it and adds the people on it to the canonical issue. The canonical issue may be the older one, the more visible one or the one with the wider scope. On GitHub, a comment reading "Duplicate of #97" makes the link, and it can be undone.

Two ideas are worth copying. People on the duplicate carry over to the parent, so nobody is lost. And the merge can be reversed, because it will sometimes be wrong.

A workable matching rule for support:

  • Same symptom, same screen, same app version: link it.
  • Same symptom, different version or operating system: link it provisionally, and flag it for engineering.
  • Similar words, different screen: keep it separate.
  • One report describing two problems: split it.

Record the version, device, operating system, country, and the time it first happened on the parent ticket. Ask only for what you don't have, and ask privately.

One check before you escalate is the store's own data. Google's Android vitals sets bad behaviour thresholds for user-perceived crash rate of 1.09% overall and 8% on a single phone model. Go above them and Play may reduce your visibility or show a warning on your listing. Vitals counts per daily active user, and Google notes Crashlytics counts per session, so the two will not match. A crash that sits on one phone model can look small overall and still cross the per-model line.

What the stores allow

Store replies are public and short, and they have rules of their own. These apply wherever you operate.

RuleApp StoreGoogle Play
Replies per reviewOne visible response, editableOne public reply, editable
LengthNo limit stated on the pages we read350 characters, plain text
When it appearsUp to 24 hoursNot stated on the pages we read
Does the user hear?Yes, and they can update their reviewPush and email. Editing a reply sends no new notice
ContentNo personal information, spam or marketing, stay on the user's commentTruthful, relevant, respectful, no soliciting or promoting. Violations can cost you the account
AutomationPersonalise rather than paste the same textGoogle discourages automated replies you intend to update by hand later
Asking for a ratingApple's API only, three prompts in 365 daysNo questions before the prompt. No incentives

Three details change how you work:

Apple also says to point download and billing problems to Apple Support, so route those away from your bug queue. And you can reset your summary rating when you ship a new version, per territory. Apple recommends doing it sparingly.

Do not trade a fix for a better rating

The urge after a bad bug is to ask people to change their rating. Asking is fine in general. Offering something for it is where trouble starts. The principle almost everywhere: a review must be the person's genuine opinion, and any reward must be disclosed and must not depend on the sentiment. Store policy is stricter. Google lists asking users to rate while offering an incentive as a violation. Apple's guidelines cover paid, incentivised or filtered feedback. This is general information and not legal advice, so check your own market.

MarketWhat applies
USFTC rule, in effect since 21 October 2024. Incentives can't carry an express or implied requirement of a particular sentiment. Groundless legal threats to get a review removed are barred
UKCMA fake reviews guidance of April 2025 covers fake reviews and concealed incentivised reviews
EUYour Europe says traders may not alter customer reviews and ratings or pay for fake reviews
AustraliaACCC guidance: incentives must apply whether the review is good or bad and be disclosed. Removing genuine negative reviews may mislead
IndiaIS 19000:2022, a standard for organisations publishing reviews online, launched in November 2022 as initially voluntary. Check its current status

Who does what

SituationOwnerFirst moveNever
New report, matches an open ticketSupportLink it, reply to the personOpen another ticket
Reports climbing on one ticketSupport leadAlert the mobile owner with count and versionsWait for a weekly review
Crash after a new releaseMobile leadHalt the rolloutKeep rolling out while you investigate
Report needs detailsSupportAsk privately for version and deviceAsk in a store reply
Reporter describes lost moneyPayments teamTreat it as a money caseLink it to a bug and move on
Request for a feature, worded as a bugProductMove it to the feature listCount it as a bug report
Report can't be reproducedEngineeringAsk for one specific detailClose as "works for me" with no reply

Stopping a bad release is the fastest fix available. On Google Play, halting a staged rollout stops delivery to new users, but those who have it keep it. Fix it with a new release if the bundle is bad. On the App Store, phased release goes from 1% to 100% over seven days and can be paused for up to 30 days in total, though anyone can still download manually. Apple allows an expedited review for a critical bug fix if you include steps to reproduce the bug on the current version.

Replies you can copy

Store replies below fit Google's 350 characters. Keep them that way.

First reply, in chat or email

Hi Kenji, thanks for telling us. Others have reported the same crash on the Payments screen and our mobile team has it. One thing would help: which app version do you have? It's under Settings, About. I'll message you when the fix is out.

Public reply on a store

Thanks for reporting this. We know Payments is crashing on launch for some people and we're working on a fix. Please contact help@pocketpay.example with your app version so we can keep you posted. Your payments and balance are not affected by this crash.

Only include that last sentence if engineering has confirmed it.

Update when there is no news

Hi Kenji, still no fix to share. The team has found the crash happens when the screen loads your saved cards, and they're testing a change. I'll write again by Thursday even if nothing has moved.

Closing reply

Hi Kenji, the crash is fixed in version 6.4.1, which is on the store now. Please update and open Payments. If it still closes, reply here and tell me what phone you're on, and I'll reopen this.

Store reply after the fix

Fixed in version 6.4.1, out now. Update the app and Payments should open normally. If it doesn't, write to help@pocketpay.example and we'll look at your case directly. Thanks for the report, it helped.

Hard case: can't reproduce, or won't be fixed

Hi Kenji, I'll be straight with you. We can't reproduce this, and it only appears on one older phone model, so we aren't planning a fix right now. A workaround is to use Payments in the browser at pocketpay.example. If that doesn't work for you, tell me and I'll see what else we can do.

A routine to start on Monday

Times are a suggested starting point and not a benchmark. Set them by your release pace.

  1. Add a required field on bug tickets: parent ticket or "none yet".
  2. Name one person per shift who checks matches.
  3. Search open tickets before opening any new one, in every language you get.
  4. Reply to each report within one working day, and link it within the same day.
  5. Set a trigger: when a parent ticket passes a number of reports in a set window, alert the mobile owner. Start with 5 in 2 hours and tune it.
  6. Check Android vitals and your crash tool whenever a parent ticket moves.
  7. On every release, list parent tickets the release closes.
  8. Message the linked people the same day the fix ships, and reply to the store reviews for that bug.

Mistakes teams make

  • Merging by keyword, so "payment failed" and "payments screen crashes" become one ticket.
  • Closing duplicates without carrying the reporter across. The merge saves time and the customer never hears back.
  • Pasting one reply on 40 reviews. Apple tells you to personalise, and readers notice.
  • Asking for a phone model in a public reply.
  • Writing "update to the latest version" before the fix has reached that person.
  • Promising a date in a store reply, which stays visible long after the date passes.
  • Counting reports and ignoring who sent them. Five reports from one customer are not five customers.
  • Offering credit for changing a rating.

What to measure

  • Ratio of reports to parent tickets. A figure near 1 during a known bug means merging isn't happening.
  • Time from first report to parent ticket reaching engineering.
  • Share of linked reporters told about the fix.
  • Wrong merges, counted as tickets split apart afterwards.
  • Reopens after a fix. High numbers suggest the fix did not hold or missed a device.
  • Reviews updated after a reply, as a sign that the follow up reaches people.

It is working when engineering sees one ticket with a real count, and customers stop reporting a bug that has already been fixed.

A worked example

This is an example scenario. The app, people and messages are made up to show how this works. It is not a customer story.

Pocketpay is a payments app. One morning its Payments screen starts crashing.

Priya Shah leaves one star on Google Play: "App crashes the moment I open Payments. Pixel 8." Lucía Fernández posts on X in Spanish: "La app se cierra en cuanto abro Pagos. @pocketpay" (The app closes as soon as I open Payments.) Kenji Watanabe writes in chat in Japanese: "支払い画面を開くとアプリが落ちます。" (The app crashes when I open the payments screen.)

Three channels, three languages, one bug. Pocketpay already has BUG-2291, "crash on opening Payments", so all three get linked and the count goes up. Reports pass the trigger, so the mobile owner is alerted and halts the staged rollout. Support asks Lucía and Kenji privately for the app version. Priya gets a public store reply under 350 characters, with an address to write to. When 6.4.1 ships, the linked list gets a message and the store reply gets edited. Because Google does not notify on edits, support also follows up on the channels where it has a contact.

What runs in Relay today

Tagging, grouping similar reports into themes, linking cases to tickets, crisis alerts and routing to the right team run in Relay today, along with drafted replies that a person approves. Sending on X and email needs each channel's token. Replies to App Store and Google Play reviews still go through each store's own developer console, so plan on that.

Jira, Linear and GitHub sync is on the way. Until then, the Relay ticket is the shared record and the team copies the summary into its tracker. If your support team drowns in duplicate bug reports, contact us. For the moment a bug becomes an outage, see handling a ticket spike. For a crash on a money screen, see money debited but payment failed.

Common questions

How many reports should turn a bug into an incident?

There is no standard number. Pick a count in a time window, such as 5 in 2 hours, and tune it to your volumes after a few releases. Check it against your crash data as well as your inbox.

Can we ask someone to change their review after a fix?

Replying to tell them it is fixed is normal, and Apple suggests replying after a fix ships. Offering a reward for a better rating breaks Google Play policy and creates legal risk in several markets. Tell them it is fixed and leave the choice to them.

Why can't we fetch old Google Play reviews through the API?

The API returns only reviews created or modified in the last week. Older reviews are available through a CSV export from Play Console. Google's page limits retrieval and doesn't say whether older reviews can be answered through the API, so reply in the console or test it.

Should we merge reports from different app versions?

Link them provisionally and flag the difference for engineering. The same symptom on two versions can have two causes. Keep the ability to split them.

Does Relay ask customers for device details in public?

No. Drafts ask for the app version and phone model privately, and a person approves each one before it goes out. Store replies stay in the store's own console.

Does Relay work with Jira or Linear?

Not yet. Jira, Linear and GitHub sync is on the way. Today the ticket lives in Relay.

Sources

See what Relay can do for your customer service

Get a personalised 30 minute demo on your own channels and policies. We show you Relay handling your real conversations, then set it up with you.

  • Built and connected for you
  • Can run in your own cloud
  • A person on every refund

Brands we work with

  • Bolt
  • Dave & Buster's
  • ETV Win
  • Malachite Cars
  • Space Angel
  • Infinity Quest
Made by Thinkiyo© 2026 Thinkiyo. Relay is a Thinkiyo product.Examples use Lumen Parcel, a fictional brand.