Card #11 · Atlassian Marketplace
Lack of bidirectional conversation sync between Slack and JSM
Merchants struggle to maintain conversation continuity between Slack threads and JSM tickets. The official integration acts as a simple forwarder, forcing agents to manually summarize Slack conversations into JSM for record-keeping and SLA reporting.
Pain score
0.57/ 1.00 · weighted product of four components
Reach0.52distinct authors (log-normalized)
Recency0.63freshness decay, half-life months
Engagement0.83upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 4 verified quotes
The official Atlassian Slack-Jira app captures the message as a ticket but it's basically a forwarder. The back and forth that follows happens in Slack, and an agent has to manually summarize the conversation into JSM after the fact.
What I actually want: thread in slack, ticket gets created in JSM with the slack thread URL attached, replies in either side post to the other automatically until the ticket closes.
The Slack-Jira app was never going to solve this because it treats every message as a ticket creation event, not a conversation.
tickets get manually copied into JSM after the slack thread resolves, which is when our ITIL person remembers.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro