Recurring issues — the week of 7 September 2026
Produced by: Run EXAMPLE-SR-01 · support project read-only · document artifact · demo values
- Scope
- 16 tickets read in this window, 2 left out because they belong to teams this reader cannot see, and 9 in the fortnight before. Because anything was hidden, every count below is stated as a minimum — this report's whole output is "this happened N times", so a cause whose tickets are partly on a team you cannot see is smaller on the page than it is in reality. A cause needs 3 tickets here; below that it is a coincidence and is not filed.
- Ranked causes
- 3 causes, worst first, with Tickets, Share of tickets read, Grade, Shared evidence, First seen, Last seen and Problem ticket. The largest holds 5 of the 16 tickets read — written as two numbers, never as a percentage, because a share you cannot see the denominator of is a share you cannot check. Every figure equals the number of ticket links printed for that cause further down the page.
- Each cause
- One subsection per cause. "Cards declined at checkout after bank verification" is held together by the label billing, carried by 5 of its tickets — computed from the tickets, not asserted by the model, and printed so you can open two of them and disagree. Under it sit the quotes, each copied word for word out of its own ticket, and every member ticket as a link.
- New this window
- 2 of the causes had no problem ticket before this run, so this run filed one for each. "Single sign-on returns to the login page after approval" already had SUP-900, so nothing was filed for it and this window's tickets were linked to the ticket that exists. Filing a second ticket for a cause somebody is already working is the fastest way to make this report worth ignoring.
- Left alone
- 4 tickets joined no cause, and the section says so rather than letting them disappear. A run that only ever reports what it found reads as complete; this one states what it could not place, and lists every group it dropped with the rule that dropped it — an invented ticket id, a quote that was not in its ticket, too few tickets, or nothing the tickets visibly share.
- What this run changed on the board
- Only what the tool results show: the problem tickets created, the ones updated, and the tickets linked to them. Then the sentence that makes the rest of it safe to run weekly — no customer ticket was closed, moved, reassigned or rewritten. The second cause, "Large exports finish successfully with an empty file", arrived on the board as one ticket with 4 linked to it instead of 4 separate conversations.