Thread 6: JSM Intake Slack Jira Context Split

Platform

Reddit

Link

https://www.reddit.com/r/jira/comments/1s3gnyh/jsm_intake_is_broken_when_everyone_just_slacks/

Key Excerpt

“we’ve got two realities: the official flow through the JSM portal (~30% of requests) and the actual flow where everything starts in slack… conversation splits - half in slack, half in jira comments. nobody knows where the real thread is.”

Why This Matches Ryva ICP

This is a textbook Slack/Jira split: official tracker vs real work channel divergence. It directly expresses missing ownership and fractured context across systems.

Underlying Problem

Intake and execution happen in Slack while governance happens in Jira, creating dual truths and broken case continuity.

Suggested Public Reply (Copy)

“Two realities” is exactly the failure signature. When requests start in Slack but lifecycle lives in Jira, teams spend time reconciling state instead of resolving work. The bridge has to preserve one canonical conversation with synced status, not duplicate threads across tools.

Suggested DM Idea (Copy)

Your post is a perfect example of context bifurcation: work starts in Slack, accountability lives in Jira, and neither side trusts the other. If useful, I can share a practical bridge model teams use to keep one thread + one state.