Jira and Slack, read together
Slack is where the team actually talks: decisions, asks and updates in channels and threads, gone from view in a day. Jira tracks engineering work in issues, epics and sprints, in the language of the team that builds. The gap between them is every request that was made in a thread and never written down, and every item in Jira whose real status is three messages deep in Slack.
Liaison reads Slack and Jira together, the way the one person who tracks everything would, and tells you what was asked, what was promised, and which of the two systems is out of date.
Where Jira and Slack disagree
- Asks made in Slack threads that never became issues in Jira, so they are owned by nobody.
- Jira statuses that stopped being true the moment someone wrote "actually, this is blocked" in a channel.
- Due dates agreed in Slack that were never changed on the Jira item.
- Decisions taken in a thread that the Jira record still contradicts.
- People notified in Slack who are not the assignee in Jira, and assignees who were never told.
Questions it answers across both
- “What did we agree to in Slack this week that is not in Jira yet?”
- “Which Jira items are marked in progress but have had no activity anywhere in ten days?”
- “What is blocked, according to the threads, that Jira still shows as on track?”
- “Who promised what to the customer in #support, and is it tracked?”
What Liaison does with Jira and Slack
- Reads the Slack channels you choose and lists the asks that have no Jira item, with the thread each came from.
- Drafts the Jira item for each untracked ask, with the owner and date from the thread, for you to confirm.
- Flags Jira items whose status disagrees with what was said in Slack, and says which message changed it.
- Writes the weekly status from both: what was asked, what moved, what is stuck, with links to the thread and the item.
What it reads and does in each
Liaison across Jira and Slack, set up with you, for $629 a month.
- Connects to Jira and Slack with access you grant and reads them as one record; nothing is replaced or re-entered.
- Does the routine work in your voice; each kind of work is approved once.
- Answers across both: what Jira says, what Slack says, and where they disagree.
On Professional we connect your tools, bring your data in and set up the first rules with you. Anything that moves money waits for your yes.
“Cut our month-end close from 4 days to 4 hours.” Marcus C., owner
$629 a month, or $500 a month on a 12-month term. Prefer to start on your own? Starter is $149 a month, self-serve, with a free trial first: 7 days, no card.
Questions
Does Liaison post in Slack on its own?
It can post, and it does so only for the kinds of messages you approved once, such as a weekly status in a channel you chose. It never creates Jira items without your confirmation on each.
Do I need to tag Liaison in every thread?
No. It reads the channels you give it access to, in full, and works out which messages are asks. You can also ask it directly in Slack.
Will it change Jira records?
Only after a yes. It drafts the item or the status change and shows you the thread it came from; you confirm, it writes.
What does it cost?
Liaison starts at $149 a month. Professional is $629 a month and Team is $2,950 a month for up to five seats. Every plan works with the tools you connect.
See it on your own business.
Thirty minutes with us, on your own tools. Bring the thing that eats your evenings and watch it get handled from your own inbox, calendar and books.
Professional is $629 a month and we set it up with you. Starter is $149 a month, self-serve, with the free trial first: 7 days, no card. Every plan is on the pricing page.