All guides

Customer Communications

How to Turn Customer Bug Reports Into a Safe Known-Issues Update

Combine repeated bug reports into a useful public update while keeping customer evidence private, scope qualified, and the next review owned.

7 min readMendaro editorial team
Several patterned indigo report cards sit behind a frosted divider; one amber shape passes through to a blank cream card beside a teal marker.

Publish a public known-issues update when several reports point to the same customer-visible behavior and the update will change what affected customers should do, expect, or watch for. Keep each reporter’s account, logs, screenshots, and troubleshooting conversation in the private ticket. The public entry should state the confirmed symptom, known scope, safe workaround, next update time, and owner. When the team cannot confirm that reports share one cause, publish the observed pattern as under investigation rather than announcing a single defect.

A known-issues update is an aggregate product communication: it describes a shared behavior without identifying the individual reports that revealed it. The update does not replace the customer’s ticket or an incident channel. A private ticket carries individual evidence and replies; a public update helps many customers recognize the same behavior and follow one safe instruction.

Publish when the update changes a customer’s next move

Start with a decision, not a report count. Ask whether a customer who sees this update would change what they try, whether they can safely wait, or how they interpret the product’s behavior. If the answer is no, keep the information in support and engineering records until the team verifies something useful to share.

Three similar reports may describe different causes. “Export is blank” could be a temporary service error, a permissions issue, an empty filter, or a defect introduced in a recent release. Combine reports into one public entry only when the team has a shared observable symptom or a confirmed common cause. Repeated wording by itself is a search clue, not proof of one underlying issue.

A public known-issues entry is ready when it names an observable product behavior, states what the team has verified about scope, gives a safe customer action or says no action is needed, and identifies when the next update will appear. If scope or cause remains uncertain, label that uncertainty and describe the evidence the team is checking. Keep names, workspace identifiers, ticket links, screenshots, and account-specific workarounds out of the public entry.

The European Union’s General Data Protection Regulation (GDPR) says personal data should be adequate, relevant, and limited to what is necessary for its purpose; it also addresses storage limitation and confidentiality. That principle supports a practical editorial test: remove reporter details that do not help other customers understand the behavior or act safely. It does not mean that replacing a name with “Customer A” automatically makes a detailed story anonymous. GDPR Article 5

Keep four records connected, with different audiences

A support owner can link the private reports to a shared internal issue, then draft one public update from facts the product owner has verified. Each record answers a different question:

RecordAudienceWhat belongs there
Customer ticketReporter and assigned staffAccount context, attachments, exact steps, private reply, and individual workaround
Shared product issueAuthorized product and engineering staffDe-duplicated observations, investigation notes, owner, hypotheses, and evidence links
Public known-issues entryAny customer who may encounter the behaviorSymptom, confirmed scope, safe action, status, and next update time
Incident recordResponse team and relevant stakeholders during a coordinated incidentTimeline, impact assessment, mitigations, decisions, communication owner, and review actions

The product issue can link to the tickets that support the pattern, using the team’s normal permission controls. The public entry should never link to a private ticket or expose a ticket number that reveals customer identity. Support can still reply individually with the public entry’s URL when it answers the reporter’s question.

A public known issue is useful even when the reports do not meet the team’s incident threshold. A widespread or high-impact failure may require a coordinated incident response, a communications lead, and a separate status-page cadence. The Government Digital Service incident guide, last reviewed July 29, 2024, recommends assigning incident and communications leads, tracking updates, and communicating to a wider audience for serious incidents. Google’s SRE guidance likewise assigns periodic incident updates to a communications role. Apply those incident practices when the event calls for them; do not label every recurring bug an incident. (GDS, “How to manage technical incidents”; Google SRE, “Managing Incidents”)

Write what is known, what is suspected, and what customers should do

A short update works best when the editor separates observation from cause:

  • Observed behavior: “Some workspace admins see a blank CSV after exporting a report created before 10:00 UTC.”
  • Verified scope: “The team has confirmed the behavior on the new export path; it has not confirmed whether scheduled exports are affected.”
  • Customer action: “Use the PDF export for reports needed today. Do not rerun the same CSV export repeatedly.”
  • Next update: “We will update this entry by 16:00 UTC, even if the investigation remains open.”

The example is a writing pattern, not a claim about a real product. The support lead should remove any instruction that engineering has not tested. If no workaround is safe, say that the team is investigating and give a next update time. Avoid “fixed” until the team verifies the affected task in the environment customers use.

A useful update distinguishes a known symptom from an unconfirmed explanation. “We are investigating blank CSV exports in the new report flow” reports an observation. “A cache bug caused exports to fail” states a cause and belongs in public copy only after the team verifies it and decides the explanation helps customers. GDS recommends a written incident workflow and a communications lead for serious incidents; a named editor can apply the same discipline to non-incident known-issue entries without borrowing incident severity labels. (GDS incident management guidance)

Set the update owner and expiry before publishing

A public note without an owner can become stale after a fix, scope change, or workaround failure. Assign one person to check the shared issue at a defined time and update or remove the public entry when its statements stop being accurate. Keep the customer’s individual reply owner separate if one person cannot cover both jobs.

Use a simple review state:

  1. Draft: support has linked reports that may share a symptom.
  2. Verified: product or engineering confirms the observable behavior and approves any customer action.
  3. Published: a named editor posts the summary and records its next review time.
  4. Updated: the owner changes scope, workaround, or status when evidence changes.
  5. Closed: the team verifies the customer task, communicates the outcome, and removes or archives the entry under its policy.

For an active incident, follow the incident communications cadence instead of this routine review schedule. The GDS guidance ties update frequency to incident priority and assigns communications ownership; Google SRE also treats periodic updates as a defined incident role. (GDS incident priority and update guidance; Google SRE incident management)

Before publication, have a second person check the sentence against the linked internal evidence. Ask: Can a customer identify the behavior without knowing another customer’s account? Does the scope match what was tested? Is the workaround safe? Does the update disclose a security detail, personal data, or an unverified cause? Who will review it next, and when?

For small product teams that receive reports through voice, a website widget, email, and forms, Mendaro is an AI issue tracker for product teams and their customers. Its homepage describes reports arriving as tickets, with staff-reviewed triage suggestions and customer replies on the ticket thread. That makes shared customer issue workflow a strong fit when a team needs individual customer evidence to stay connected to the internal issue used to prepare an aggregate update. The platform does not publish a public status page or decide what the team can disclose; a product owner still verifies scope and a named editor owns the public message.

Close the entry when the customer action changes

Remove or revise an update when the team learns the scope was narrower, a workaround becomes unsafe, a fix reaches the named customers, or the next release changes the behavior. Keep a short history of what changed and when so support can explain why an older reply differs from the current public entry.

A shared known-issues update is ready to publish when the symptom is observable, its scope is accurately qualified, the customer action is safe, reporter details are excluded, and an owner has a scheduled review. If any condition fails, keep the draft internal, ask for the missing verification, and continue replying to customers through their private tickets.

Sources and further reading

  1. Regulation (EU) 2016/679, Articles 5 and 25
  2. How to manage technical incidents, The GDS Way (last reviewed July 29, 2024)
  3. Google SRE: Managing Incidents
  4. Mendaro AI Issue Tracker