memory: Syncro bot alerts must include ticket link
Feedback from Mike (Bardach #32387): every Syncro ticket bot-alert needs a clickable link (https://computerguru.syncromsp.com/tickets/<internal_id>). post-bot-alert.sh posts raw text, so the URL must be in the message. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -27,6 +27,7 @@
|
|||||||
- [Mike — font preference](user_font_preference.md) — Mike prefers Lucida Console for monospace UI.
|
- [Mike — font preference](user_font_preference.md) — Mike prefers Lucida Console for monospace UI.
|
||||||
|
|
||||||
## Feedback
|
## Feedback
|
||||||
|
- [Bot alerts need a ticket link](feedback_bot_alert_ticket_link.md) — Syncro ticket bot-alerts MUST include a clickable link: https://computerguru.syncromsp.com/tickets/<internal_id> (internal id, not ticket number). post-bot-alert.sh posts raw text; put the URL in the message.
|
||||||
- [Scheduling = coord todo, not schedulers](feedback_scheduling_via_coord_todo.md) — Defer future work as a coord todo (POST /api/coord/todos; needs text + created_by_user + created_by_machine) for a later session to pick up. NOT /schedule remote CCR agents (no vault/creds there) or local scheduled tasks.
|
- [Scheduling = coord todo, not schedulers](feedback_scheduling_via_coord_todo.md) — Defer future work as a coord todo (POST /api/coord/todos; needs text + created_by_user + created_by_machine) for a later session to pick up. NOT /schedule remote CCR agents (no vault/creds there) or local scheduled tasks.
|
||||||
- [Attribution is read, never inferred](feedback_attribution_from_identity.md) — Who-did-what (user+machine) comes ONLY from identity.json + users.json + git authorship. Never infer from hostname patterns, the userEmail hint, or memory. The "5070" box is Mike's. sync.sh reconciles git config to identity.json; /save renders the User block via whoami-block.sh.
|
- [Attribution is read, never inferred](feedback_attribution_from_identity.md) — Who-did-what (user+machine) comes ONLY from identity.json + users.json + git authorship. Never infer from hostname patterns, the userEmail hint, or memory. The "5070" box is Mike's. sync.sh reconciles git config to identity.json; /save renders the User block via whoami-block.sh.
|
||||||
- [D2TESTNAS SSH Access](feedback_d2testnas_ssh.md) — Use root@192.168.0.9 with Paper123!@#, not sysadmin.
|
- [D2TESTNAS SSH Access](feedback_d2testnas_ssh.md) — Use root@192.168.0.9 with Paper123!@#, not sysadmin.
|
||||||
|
|||||||
22
.claude/memory/feedback_bot_alert_ticket_link.md
Normal file
22
.claude/memory/feedback_bot_alert_ticket_link.md
Normal file
@@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
name: feedback_bot_alert_ticket_link
|
||||||
|
description: Syncro/ticket bot alerts must include a clickable link to the ticket
|
||||||
|
metadata:
|
||||||
|
type: feedback
|
||||||
|
---
|
||||||
|
|
||||||
|
Every `#bot-alerts` post about a Syncro ticket MUST include a clickable link to that ticket.
|
||||||
|
`post-bot-alert.sh` posts the raw message verbatim — it does NOT auto-append a link — so the URL
|
||||||
|
must be in the message text. Discord auto-links bare URLs.
|
||||||
|
|
||||||
|
**Why:** Mike wants to click straight through to the ticket from the alert feed; an alert without
|
||||||
|
the link makes him hunt for it (flagged 2026-06-05 on Bardach #32387).
|
||||||
|
|
||||||
|
**How to apply:**
|
||||||
|
- Syncro ticket URL uses the **internal ticket id**, NOT the ticket number:
|
||||||
|
`https://computerguru.syncromsp.com/tickets/<internal_id>` (e.g. #32387 -> id 112248434 ->
|
||||||
|
`https://computerguru.syncromsp.com/tickets/112248434`).
|
||||||
|
- Put the URL on its own line after the summary, or inline. To edit an already-posted alert,
|
||||||
|
PATCH `https://discord.com/api/v10/channels/<channel>/messages/<message_id>` with `{content}`
|
||||||
|
(the bot can edit its own messages; token from `projects/discord-bot/bot-token.sops.yaml`).
|
||||||
|
- Applies to any ticket-related alert (create, update, close, comment, billing). See [[feedback_syncro_html]].
|
||||||
Reference in New Issue
Block a user