Summary

We would like to request the development of a new API endpoint related to chat tools integration in Jira Service Management Cloud.

Currently, we can use the following endpoints:

• Get chat channels
• Create chat channel
• Unlink chat channel

(reference link: https://developer.atlassian.com/cloud/incidents/rest/api-group-chat-tools/#api-group-chat-tools )

However, there is no API endpoint available to add/link an already existing Slack channel to an Incident.

Proposed Future State:

Currently, Jira Service Management Cloud enables users to create, fetch, and disconnect Slack channels via API, but does not support linking an existing Slack channel to an incident through an API call. This gap necessitates manual intervention to associate externally created private channels with incidents, which runs counter to automation goals and can introduce operational risks related to efficiency and information segregation .

Teams often automate both incident creation and Slack private channel setup via external systems for security and workflow reasons. However, the lack of an API to link an existing channel means manual channel selection is required—an impractical step in automated workflows. Enabling an API-based method to link pre-created Slack channels to incidents will allow seamless integration, precise channel-to-incident mapping, and prevent information from multiple incidents from being inadvertently mixed in a single channel .

A sample endpoint is proposed:
 

POST 

/jsm/incidents/cloudId/{cloudId}/v1/incident/{issueID}/chat/channel/link

BODY (Sample)

{
  "connectionId": "acacdbbb-09eb-42df-b3c2-78532c60eeee",
  "channelType": "slack",
  "issuerId": "301893",
  "projectId": "10002",
  "channelId": "C07S5Q41T9R",
  "channelName": "security-interview-sir-901"
}

 
This enhancement will remain valuable even if JSM later supports private channel creation, as there will still be scenarios requiring external channel creation and linkage. From both a security automation and operational efficiency perspective, automating the connection between incident and private channel is essential .

Atlassian Support has clarified that the use of internal APIs is not an option and that a new REST API endpoint must be considered through a suggestion ticket .

Alternative (e.g. Third Party Plugin):

NA