Jira and Slack, ready to switch on
New issues in the projects you name, the transitions you care about and comments land in the Slack channel you choose, with the assignee and a link to the issue. You paste two keys in your account and it runs, in about ten minutes.
No setup fee, cancel any month, and a person on live chat if a key doesn't work.
More with these apps: all Jira integrations · all Slack integrations
What moves, and when
The details you would normally get after a sales call. Here they are up front.
| What | Direction | When | Rule |
|---|---|---|---|
| New issue in the projects you name | Jira to Slack | Within seconds | Key, summary, type, priority and assignee, in the channel you choose |
| Transitions | Jira to Slack | Within seconds | The ones you care about, usually In progress and Done, posted in that issue's thread |
| Comments | Jira to Slack | Within seconds | Author and the first lines; internal comments stay in Jira if you'd rather they did |
| Blockers | Jira to Slack | When the priority or the flag changes | A post of its own in the channel you keep for work that needs a person now |
| One key, one thread | Jira to Slack | Every event | Everything about an issue sits under the first post about that issue |
Ten minutes of your time, then it's ours
- Pay and open your accountCard or invoice, about two minutes. This integration is already selected.
- Paste the Jira API token and the Slack bot tokenEach has a short guide. About eight minutes. If one doesn't work, a person joins the chat.
- Create one test issueA minute or two. Create a issue in Jira and watch the post arrive in the channel. From then on we watch it for you.
When Jira or Slack changes its API, we fix it within a working day. You don't get a ticket to solve.
- Everything in the table above, with monitoring on.
- Fixes when either app changes its API.
- A person on live chat, replies within a working hour.
- Custom logic beyond the table is priced separately.
No setup fee, cancel any month
Before you decide
Can we create a issue from a message?
Not in this one. It runs into the chat so the team sees the board without living in it. If turning a message into a issue is what you actually want, describe it and we price it.
How do we keep it quiet enough to read?
Pick the projects and the moves worth posting, and leave the rest out. You can add more later; taking noise away after people have muted the channel is harder.
Anything to know about Jira?
This is for Jira Cloud. Server and Data Center use a different API and aren't covered here.
Anything to know about Slack?
The bot has to be invited to a channel before it can post there; that's one command in Slack.
What if mine is a bit different?
Tell us what should go where in plain words. Small changes to the rules above are usually free; bigger ones we price the same day and build into the same account.
