AI assistant for safe, reliable productivity with code, collaboration, and integrations.
Mushka
0Popularity
About Mushka
Mushka is a Slack-integrated bot that monitors designated channels and proposes Jira ticket drafts based on conversations. It reads messages only in channels explicitly invited to and drafts tickets with suggested titles, projects, and assignees. Each proposal requires a human team member to click Approve before any action is written to Jira. The tool maintains an audit log of all approved actions, including what was proposed, who approved it, and the resulting Jira ticket details. Raw Slack messages are processed for ticket drafting and then deleted, ensuring Slack remains the primary record. Mushka connects to Jira via OAuth and restricts its actions to the specific projects authorized by the user. All credentials are encrypted at rest with customer-specific keys, and data is not used to train AI models.
Key features
- Slack message monitoring in invited channels
- Jira ticket drafting with suggested titles and assignees
- Human approval required for all Jira writes
- Audit logging of approved actions
- Project-scoped Jira access
- Encrypted credential storage
- Message processing without data retention
- OAuth-based Jira connection
Use cases
- Converting Slack discussions into tracked Jira tickets
- Reducing manual ticket creation from conversations
- Streamlining status updates and bug reports from team chats
Pros
- Drafts Jira tickets directly from Slack conversations
- Requires explicit human approval before writing to Jira
- Maintains an audit log of all approved actions
- Processed messages are deleted after use
- Credentials encrypted per customer
Cons
- Limited to Slack and Jira integrations
- No free tier or trial mentioned
- Requires manual installation and channel invites
Frequently asked questions about Mushka
What can Mushka see in my Slack workspace?
Mushka only reads messages in channels explicitly invited to using /invite @Mushka. It does not access DMs, private channels it wasn’t invited to, or workspace-wide content.
Can Mushka change Jira without my approval?
No. Mushka proposes actions in Slack, but executes them only after a human team member clicks Approve. Proposing and executing are separate processes.
Where does my Slack data go after Mushka processes it?
Raw Slack messages are deleted after processing. Activity digests are sent to large-language-model providers under agreements that prohibit training on your data.
Does Mushka store my Slack messages or build a copy of my workspace history?
No. Slack remains the primary record. Mushka holds raw messages only briefly to draft tickets, then deletes them, and retains only an audit log of approved actions.
How does Mushka handle credentials and data security?
Slack and Jira tokens are encrypted at rest with customer-specific keys (AES-256-GCM) and decrypted only at the moment of use. All actions are scoped to the projects you authorize.
What integrations does Mushka currently support?
Mushka currently integrates with Slack and Jira. Linear, GitHub Issues, and Microsoft Teams are planned for future releases.
