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 we switch it on for you.
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 |
How to set up Jira and Slack
A few minutes of your time, then it's ours.
- Choose Jira and SlackPress Connect. This pair is already selected on the checkout page at $39 a month, and there's nothing else to pick.
- Pay and open your accountCard or invoice, about two minutes. The account opens with this integration waiting for its two keys.
- Paste the Jira API token and the Slack bot token
- Jira API token: open id.atlassian.com/manage-profile/security/api-tokens and press Create API token. Full Jira guide
- Slack bot token: open api.slack.com/apps and create an app from scratch in your workspace. Full Slack guide
Each screen carries the full guide with the exact menu names, about eight minutes for both. - We check both keysEach key is checked against Jira's and Slack's own API the moment you paste it. If one doesn't pass, the screen says what to fix, and a person joins the chat if that isn't enough.
- Create one test issue, then we switch it onA minute or two. Create a issue in Jira and watch the post arrive in the channel. From then on we watch it for you. A person checks the setup and switches it on, within a working day.
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, weekdays 10:00 to 19:00 EET.
- Custom logic beyond the table is priced separately.
What it will cost once you can switch it on yourself. While we're in beta we connect it by hand and don't charge for it.
Ways to connect Jira and Slack
Two ways people connect these two, and what each one asks of you.
Before you decide
Can we create a issue from a message?
Not in this one; it runs into the chat. If a message should become a issue, describe it and we price it.
How do we keep it quiet?
Name the projects and the moves worth posting. Everything else stays on the board.
Can we post from more than one project?
Yes, and each project can have its own channel. A support project in one place and a platform project in another is the usual split, and it keeps both channels readable.
Does Jira integrate with Slack?
Yes. With this pair, new issues in the projects you name, the transitions you care about and comments are posted to the Slack channel you choose, with the assignee and a link to the issue. You paste a Jira Cloud API token and a Slack bot token in your Dovetly account; nothing is installed in either app. $39 a month, flat.
How can I receive Jira notifications in Slack?
Paste two keys: a Jira Cloud API token from id.atlassian.com and a Slack bot token from api.slack.com. Tell us which projects and transitions are worth posting, invite the bot to the channel, and the next issue lands there with its key, summary, type, priority and assignee. Everything about one issue stays in one thread.
Can you use Slack as a ticketing system?
Not with this pair on its own. Jira stays where tickets are created, assigned and closed; Slack is where the team hears about them, one thread per issue. A blocker gets a post of its own in the channel you keep for work that needs a person now.
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 within a working day and build into the same account.
