Link Issue
link_issueLinks an existing external ticket or GitHub pull request to a Sentry issue by URL, adding a reference without creating the ticket or changing issue status.
Instructions
Link an existing external ticket or GitHub pull request to a Sentry issue by URL: Jira, GitHub, GitLab, Bitbucket, Azure DevOps, or an installed Sentry App such as Linear. Adds a reference only; it does not create the ticket or change the issue status (use update_issue).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"externalIssueUrl": "<externalIssueUrl>"
},
"name": "link_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Extra form values by field name, for a Sentry App that requires them. | |
| appSlug | No | Installed Sentry App slug. Inferred for Linear and Shortcut URLs; specify it for other Apps. | |
| issueId | No | The issue short ID, e.g. `PROJECT-1Z43`. | |
| issueUrl | No | The issue URL, e.g. https://my-org.sentry.io/issues/PROJECT-1Z43 | |
| regionUrl | No | ||
| integrationId | No | Native integration ID, only needed when multiple installations match the URL. | |
| externalIssueUrl | Yes | URL of the existing external ticket or GitHub pull request. For Sentry Apps, the canonical issue URL from the provider. | |
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | ||
| issueId | Yes | ||
| issueUrl | Yes | ||
| externalIssue | Yes | ||
| organizationSlug | Yes |