-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Integration - Slack
-
None
-
1
-
Severity 3 - Minor
Issue Summary
Jira work item links pasted into Slack Direct Messages (DMs) do not consistently unfurl into preview cards. The same link may unfurl on one attempt and remain as a plain URL on the next, within the same DM conversation. In channels where the Jira Cloud app has been invited as a member, unfurling works reliably as expected.
Additionally, when a link does unfurl in a DM and the user clicks "Preview in Slack" to open the sidebar panel, the panel may return a "Jira access required" error (e.g., "To view this work item, ask your Jira admin for access to [site name]"), even though the user has valid Jira permissions and can open the same link in their browser without issue.
Steps to Reproduce
- Ensure the Jira Cloud for Slack app is installed and the user is logged into the integration
- Open a Direct Message (DM) conversation with another Slack user
- Paste a full Jira work item URL into the DM and send the message
- Observe whether the link unfurls into a preview card
- Repeat step 3 several times in the same DM conversation and note the inconsistent behavior
- If the link does unfurl, click "Preview in Slack >" on the card to open the sidebar panel
Expected Results
- The Jira link should consistently unfurl into a preview card showing work item details (summary, status, assignee, etc.), the same way it does in channels where the Jira Cloud app is a member
- Clicking "Preview in Slack" should open the sidebar panel and display the work item details without error
Actual Results
- Unfurling in DMs is inconsistent. The link sometimes renders as a rich preview card and other times remains as a plain URL with no preview
- When the card does appear and the user clicks "Preview in Slack," the sidebar panel displays a "Jira access required" error despite the user having valid project access
- Opening the same link directly in a browser works without issue, confirming this is not a permissions problem
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available