Update collection ticket comment in GitLab server (on-prem)
Issue Tracking API · write, waits for approval · 100% field coverage
Your agent can update collection ticket comment in GitLab server (on-prem) through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It changes data in the customer's GitLab server (on-prem) account, so it stops with the exact request until a person approves it. Apideck adds the customer's GitLab server (on-prem) credentials, so no token ever reaches the agent.
The call
PATCH https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}/comments/{id}
Headers: x-apideck-service-id: gitlab-server, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-ticket-comments-update. Agent operation id: unified.issue-tracking.collectionTicketCommentsUpdate.
| Parameter | In | Description |
|---|---|---|
| id · required | path | ID of the record you are acting upon. |
| collection_id · required | path | The collection ID |
| ticket_id · required | path | ID of the ticket you are acting upon. |
Body fields
| Field | Type | Description |
|---|---|---|
| body | string | Body of the comment |
More for collection ticket comments in GitLab server (on-prem)
list_collection_ticket_commentscreate_collection_ticket_commentget_collection_ticket_commentdelete_collection_ticket_comment
Update collection ticket comment in other Issue Tracking apps
The same call works for each of these; only the service id changes.