Skip to content
Sign inRequest access

Close the loop

Fixing a reported bug is only half the work; telling the person who reported it is the other half. Close the loop connects a resolved report to the “what’s new” surfaces: it drafts a changelog entry from the fix, and, when the report came from an extension tester seat your team enrolled, lets you send that person a single, quiet notification that the issue is resolved.

The email path is deliberately narrow: the only address it can reach is one of your own tester seats. An address a visitor typed into the public snippet widget is never a target.

When a report is resolved and belongs to a project, its detail view offers Add to changelog. This creates a changelog entry pre-filled from the report and carrying a link back to it.

  1. Resolve the report through the normal status lifecycle.

  2. On the resolved report, choose Add to changelog. uMarker creates a draft entry with:

    • the report’s title (or the first 120 characters of its comment) as the entry title,
    • an empty body for you to write,
    • the fixed tag, and
    • today’s date in the platform’s business timezone — Asia/Riyadh unless the operator changes it, not your own profile timezone.
  3. Open the project’s Changelog tab, write the body in safe markdown, adjust the title, tag, or date, then Publish it.

The entry is always created as a draft; nothing is ever auto-published. It stores the id of the report it came from, so you can trace an entry back to the bug it resolves. Once published, it appears on the public changelog page and in the in-widget What’s new feed, which is how a returning visitor learns the fix shipped, with no email required.

That link is only read in one direction. The report’s own screen never shows the entry it produced: reload the report and nothing marks it as announced, and Add to changelog is offered again — pressing it a second time creates a second draft.

When you publish a changelog entry that was created from a report, you may tick notify reporter to email that reporter once. This is the privacy-critical part of the feature, and the boundary around it is narrow.

Of the two addresses a report can carry, only one is ever a mail target:

  • A tester seat address: one belonging to an authenticated widget user — an extension tester your team enrolled by name and email — who was signed in when they filed the report. This is the only address the reporter email can reach.
  • A submitted address: a submitter_email typed into the public snippet widget. Anyone can type anything there, so uMarker keeps it for your triage screen and never sends platform mail to it.

The reporter-email option is offered only when the linked report came from an authenticated widget user. For a public-snippet report, no email is offered and none can be sent: mailing an address a stranger typed would weaponize uMarker’s sending domain against whoever really owns it.

Sending to the reporter is never automatic: resolving a report never emails the reporter, and publishing an entry emails them only if you tick the notify option on that publish. When you do opt in, the notification is queued, and every gate is re-checked at send time, not just at the button:

  1. Still eligible: the entry is still published and has not already notified this reporter (the send is idempotent: it happens at most once per entry).

  2. Still a tester seat: the address still resolves to the authenticated widget user who filed the report.

  3. Not suppressed: the address is not on the account’s suppression list.

  4. Under the cap: your account has sent fewer than 100 reporter emails in the last hour — a blast-radius backstop. The number lives in the platform’s own deployment configuration: there is no control for it in your dashboard, and none in the operator console either.

  5. Claimed atomically: the entry is marked notified before the mail goes out, so a retry or a concurrent worker sends nothing. If the queue itself refuses the message, the claim is released, because then provably nothing was sent, and a reporter who silently never hears back is the failure worth avoiding.

The email is a plain, transactional note (“An update on the feedback you reported”) sent from the shared uMarker sending identity, never a per-tenant brand. It carries the entry’s title and body, an unsubscribe link, and a See what’s new button pointing at the project’s public changelog. That button is the one conditional part: the public page is addressed by the project’s widget key, so revoking that key leaves the email with title, body and unsubscribe and nothing to click through to.

It is written in your brand’s language — the locale saved by the earliest admin on your account, or by its earliest member where nobody holds the admin role, and Arabic when that person has saved none. An English email pointing at an Arabic changelog page is two products. It is not picked from the page the reporter was reading: a tester who filed through an English page on an Arabic-locale account gets an Arabic email.

Opening the unsubscribe link asks; it does not write. The suppression is only created when the reader confirms it on that page.

That split matters because the link never expires, and a mail client that prefetches links, or a corporate URL scanner that opens every href in an inbound message, would otherwise suppress that person permanently without a human ever seeing the page.

The result page branches on the address’s current state rather than on the last action, so re-opening the same link after unsubscribing offers a resubscribe button instead of asking the question twice. The undo stays available after the tab is closed.

A suppressed address stops receiving these emails from your account only. The list lives at /email-suppressions: a searchable screen of every suppressed address with the reason and the date, and a Resume email button on each row, which is the tenant-side half of the reporter’s resubscribe.

Nothing in the navigation links to it yet, so reach it by typing that path. It is the page that answers “why didn’t my customer get the email?” without guesswork. Reading it needs extension.view; resuming an address needs extension.update.

Emailing someone who only typed an address into a public form would require proving they own it first: capture-time confirmation and bounce handling. This feature deliberately does not attempt that. Instead, the in-widget What’s new feed and the public changelog page already close the loop for returning visitors, without sending anything to an address a stranger typed. Survey responses are anonymous and carry no address at all, so a report opened from a survey has no reply channel either, by design.