Skip to content

Display name renders incorrectly for certain transactions

Symptom

The display name doesn't render properly for certain transactions. Reported by the owner, 2026-06-21. (First ticket β€” also the worked example for the new I-NNN issue queue.)

Source

  • Capture the specific tx id(s) + a wrong-vs-expected name example on first investigation.

Investigate

  • Reproduce: which transactions show the wrong display name, and what should it be?
  • Hypothesis to check (don't assume): the display-name template / token rendering β€” tokens = raw data, templates = presentation (see [[feedback_honor_system_design]] and docs/matching-redesign.md doc-type display templates). It could instead be a data-shape issue on the affected txs.

Escalation

  • If the cause is structural (template / token plumbing, a tx data-shape problem, routing), open a T-NNN task for the fix and link it here (set frontmatter task: T-NNN). A one-off data correction can stay ticket-only.

2026-07-01 β€” closed (stale / superseded)

Closed as stale β€” the first ticket, a vague placeholder ('display name renders incorrectly') with no tx captured + no investigation. The concrete display-name issues that were actually reported got their own tickets + fixes (I-003β†’T-090; the merchant+date-instead-of-UUID fix). Reopen with a specific tx if one recurs. [owner: close I-001] - Source (edit): EOP Local Assistance (fork) Β· session edb0abc7-6373-449b-8e31-379fd38d391b