Create collection ticket in GitLab server (on-prem)
Issue Tracking API · write, waits for approval · 100% field coverage
Your agent can create collection ticket 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
POST https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets
Headers: x-apideck-service-id: gitlab-server, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-tickets-add. Agent operation id: unified.issue-tracking.collectionTicketsAdd.
| Parameter | In | Description |
|---|---|---|
| collection_id · required | path | The collection ID |
Body fields
| Field | Type | Description |
|---|---|---|
| parent_id | string | The ticket's parent ID |
| type | string | The ticket's type |
| subject | string | Subject of the ticket |
| description | string | The ticket's description. HTML version of description is mapped if supported by the third-party platform |
| status | string | The current status of the ticket. Possible values include: open, in_progress, closed, or - in cases where there is no cl |
| priority | string | Priority of the ticket |
| assignees | array | |
| due_date | string | Due date of the ticket |
| tags | array |
More for collection tickets in GitLab server (on-prem)
list_collection_ticketsget_collection_ticketupdate_collection_ticketdelete_collection_ticket
Create collection ticket in other Issue Tracking apps
The same call works for each of these; only the service id changes.
GitHubGitHub Enterprise Server (on-prem)GitLabJiraLinearLinear Multiworkspace