Your fly on the wall. With a Jira account.

How it works

1. 01 Install in Slack

   One OAuth click adds Mushka to your workspace and signs you in to the dashboard. No new accounts, no passwords.

2. 02 Connect Jira

   Authorize Jira once from the dashboard and pick the projects Mushka is allowed to touch. Approved tickets are written straight to them.

3. 03 Invite Mushka

   /invite @Mushka to the channels you want watched — the invite is the consent. From there, Mushka drafts tickets in-channel and writes nothing without an Approve click.

A bot in your Slack has to earn it.

Mushka is built so that reading is minimal and writing requires a human. Not as a policy promise — as architecture.

Every write needs an approval

Mushka can propose freely, but it cannot touch your tracker until someone on your team clicks Approve. Every executed action lands in an audit log: what was proposed, who approved it, what happened.

Your messages aren’t stored

Raw channel messages are held just long enough to build the next activity digest, then deleted. Slack stays the source of truth for your history — we never build a copy of it.

Credentials are encrypted per customer

Slack and Jira tokens are encrypted at rest with keys derived per customer (AES-256-GCM) and decrypted only at the moment of use.

Scoped to the projects you connect

Every action — reads included — is checked against the Jira projects you connected. Out of scope means refused, not retried. And your data is never used to train AI models.

The full detail is in our privacy policy.

Common questions

What can Mushka see?

Only the channels your team explicitly invites it to with /invite @Mushka. No DMs, no private channels it wasn’t invited to, no workspace-wide access.

Can it change Jira without asking?

No. Proposing and executing are separate machinery, and the execute path only runs with a human approval attached. A wrong proposal costs your team one Reject click, not a cleanup.

Where does our data go?

Activity digests are processed by large-language-model providers (Anthropic by default) under agreements that prohibit training on your data. Raw messages are deleted after processing; the audit log of approved actions is retained as your business record.

We’re not on Jira. We’re not even on Slack.

Today Mushka is Slack + Jira. Linear, GitHub Issues, and Microsoft Teams are on the roadmap — join our pilot program and the integrations you need move to the front of the line.

What does it cost?

A monthly subscription priced per developer. Ask for pricing and you’ll get a number from a human within one business day.