Issue Summary

Jira link unfurling (previews) does not work in Slack channels when the user is part of a Slack Enterprise Grid with multiple workspaces, even though the Jira + Slack integration is properly connected.

Steps to Reproduce

1. Have a Slack Enterprise Grid setup where users are members of multiple workspaces

      2. Connect the Jira Cloud site to the Slack workspace via the Jira Cloud for Slack integration

     3. Paste a Jira issue link (e.g., https://yoursite.atlassian.net/browse/PROJ-123) in a Slack               channel (public or private)

  4. Observe that the Jira link preview (unfurl) does not appear

Expected Results

The Jira issue link should unfurl and display a rich preview showing the issue summary, status, assignee, and other key fields — regardless of which workspaces the user belongs to within the Enterprise Grid.

Actual Results

The Jira link is not unfurled and no preview is displayed. The link remains as plain text. This occurs because the workspace identifier sent in the unfurl request may not match the workspace that has been connected to the Jira site, which can happen non-deterministically for users who are part of multiple workspaces within a Slack Enterprise Grid.

Workaround

Ensure that all Slack workspaces within the Enterprise Grid that users are members of are connected to the Jira Cloud site. This can be done by an admin adding the additional workspace connections via the Jira Slack integration settings. This allows the unfurl request to be accepted regardless of which workspace identifier is included in the request.