/clientfeedback
Posts a client-facing status update to the client issue and updates its labels.
Usage
/clientfeedback [time]
Parameters
| Parameter | Required | Description |
|---|---|---|
| Time | No | Time spent, in GitLab format (e.g. 30m, 1h, 2h30m) |
What It Does
1. Determine Context
Reads the current branch name to extract the development issue IID, then fetches the dev issue to find the client issue cross-reference (vinum/vinum#XXXX).
2. Determine Target Stage
Checks whether the branch was merged to main or staging:
- Merged to
main→Stage::Release - Merged to
staging→Stage::Customer Test
3. Draft a Client Comment
Composes a German, non-technical comment summarizing what was done. The comment is:
- Concise and professional
- Free of code, class names, or internal jargon
- No salutation or goodbye
You review and approve the comment before it is posted.
4. Post and Update
- Posts the approved comment to the client issue
- Tracks time via
/spend(if time parameter provided) on both client and dev issues - Updates client issue labels to the correct stage
- Reassigns the client issue to its original author
Prerequisites
- You must be on a feature branch created by
/clientissue - Work must already be committed, pushed, and merged (via
/rolloutand/merge)
Example
/clientfeedback 1h
Posts the status update and logs 1 hour of time spent.