feat(lead): Erwähnungen in Lead-Skills aufnehmen
- Adressaten und Betroffene werden als echte Mentions geschrieben (Basecamp `person:<id>`-Link, Zammad `data-mention-user-id`), damit sie benachrichtigt werden - Sascha wird nicht erwähnt, da Schreibzugriffe über seinen Account laufen - Basecamp-Kommentare bleiben ohne `--notify`; Erinnerungen bleiben bei A3 - Betrifft lead-backlog, lead-meeting-followup, lead-meeting-prep und lead-radar (inkl. references/execute.md)
This commit is contained in:
1 parent
38780da558
commit
27eefdc9cf
5 files changed
+24
-4
No files matched your search
@@ -37,6 +37,11 @@ Load the `basecamp` skill before any Basecamp CLI call. Check flags with `baseca
|
||||
|
||||
Show the comment in the proposal exactly as it will be posted, marker included.
|
||||
|
||||
**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`.
|
||||
|
||||
- Basecamp: `[@Vorname Nachname](person:<person-id>)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal.
|
||||
- Zammad (internal note, `text/html`): `<a href="<zammad-url>/#user/profile/<uid>" data-mention-user-id="<uid>">Vorname Nachname</a>`, uid via `GET /api/v1/users/search?query=<login>`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group.
|
||||
|
||||
## Steps
|
||||
|
||||
### 1. Pick the recording
|
||||
|
||||
Reference in new issue
Block a user