Connector · Project management
An AI coworker for Jira and Confluence, in Slack.
Search and update Jira issues and read Confluence pages without leaving Slack.
- Works in
- Slack
- Connects by
- Sign in with Jira and Confluence
- Can do
- 6 things, each with a switch
- Price
- Included on every plan
What Doozy can do in Jira and Confluence
Doozy searches and updates Jira issues and reads and writes Confluence pages, through Atlassian's own MCP server, as the person who connects it. Jira and Confluence's own server provides the tools, so what Doozy can do there is what Jira and Confluence offers and grows as they add to it. Each tool has a switch in Doozy.
- Search Jira issues with JQL or plain words
- Read an issue with its comments, transitions and history
- Create a Jira issue, edit one, or move it through its workflow
- Comment on an issue, log time, and read boards and sprints
- Search Confluence and read a page, its comments and its versions
- Create or update a Confluence page, and comment on one
Things people ask
In a thread, after @Doozy. It answers in that thread, with what it did.
@Doozy which Jira tickets in SUP are still open after 7 days? Sheet, with assignee.
@Doozy move SUP-412 to In Review and comment that the fix is on the staging branch.
@Doozy summarise the Confluence runbook for the nightly export, in five lines.
@Doozy write up this thread as a Confluence page under Incidents.
How to connect Jira and Confluence
No keys to paste: Jira and Confluence asks you to approve Doozy, the way it does for any app, and you can revoke that there any time.
- 1
Add Doozy to your Slack and open the Integrations page in the web app.
- 2
Pick Jira and Confluence and click Connect. Jira and Confluence's own sign-in asks you to approve Doozy.
- 3
Choose which of its tools Doozy may use, and mention @Doozy in a thread.
What stays off, and what's always true
Doozy works like a teammate, so it doesn't stop to ask. You decide what it can reach.
Off until you say so
- Deleting issues, comments and attachments, which Atlassian itself keeps off until an admin allows them
Always
- Every task runs in its own isolated workspace. Credentials stay outside it.
- Every tool has a switch. Tools that delete or overwrite start off.
- Every action it takes is on the audit log, with who asked and what happened.
- Owners and admins connect tools and choose switches. Members can only look.
More in Security and AI & Data Use.
Works well with
One ask often crosses tools: a Sentry error becomes a GitHub pull request and a Linear issue. Doozy uses whichever it needs.
Questions people ask before they connect Jira and Confluence
- Does it work with Jira Server or Data Center?
- Doozy connects to Atlassian's own hosted MCP server, which is built for Jira Cloud and Confluence Cloud.
- Can Doozy see our Jira and Confluence credentials?
- No. Every task runs in its own isolated workspace, and credentials stay outside it: they're added to each call on its way out. Nothing it reads or writes there can expose a key.
- Will it change things in Jira and Confluence without asking?
- It works like a teammate, so it doesn't stop to ask, and you decide what it can reach. Tools that delete or overwrite start switched off, you can switch off any other, and every action it takes is on the audit log with who asked.
- Who can connect it?
- Owners and admins of your Doozy workspace. Members see what's connected and can't change it. Everyone in your Slack can ask Doozy once it's connected.
- What does it cost?
- Nothing extra. Every integration is included on every plan, and the 14-day trial needs no card.
Something else? Write to [email protected].
Your next hire is one mention away.
Add Doozy to Slack and hand it the thing that's been waiting on someone all week. It comes back done, and it starts learning how your team works from the first ask.
- 14 days free, no card
- One price for the whole team
- Nothing billed until you pick a plan