How it works
- Connect your Jira site. An admin connects Jira from Settings → Integrations and approves Crumb on Atlassian's consent screen. Crumb works with Jira Cloud. If the site has a single project, it becomes the default.
- Decide what's worth building. Feedback arrives from the in-app widget, a forwarded email, Slack's
/crumbcommand, or the API, tied to an account and its ARR. Related requests group into one initiative, so you see the combined revenue waiting on the same work. - Create the issue from the thread. In the thread sidebar's Engineering card, click Create ticket. The title and description start as the feedback itself; pick a project and send. Admins and PMs can create tickets.
- Let AI write the first draft (Cloud). On Crumb Cloud's Team plan and up, Suggest with AI drafts the title and body from the feedback, the ten most recently updated issues in your default project, and your GitHub README if a repo is connected. You edit it before anything is sent.
- Follow engineering status. With a Jira webhook in place, every status change on the issue updates the Engineering field on the Crumb item. Crumb's own status doesn't move by itself: when you mark the item Shipped, the customer who sent it through the widget hears back.
What syncs
| What | Direction | When |
|---|---|---|
| Title and description | Crumb → Jira | When you create the issue |
| Issue key and link | Jira → Crumb | On creation, shown in the Engineering card |
| Issue status | Jira → Crumb | On each status change, via webhook |
| Recent issue titles | Jira → Crumb AI | When you ask for an AI draft (Cloud) |
| Crumb status, replies, attachments | Not synced | Jira never sees customer replies, and Crumb doesn't edit the issue after creating it |
A few limits worth knowing. Each workspace connects one Jira site: the first one your Atlassian account can access. Issues are created as the Task type. The project picker lists up to 50 projects. The description arrives as plain paragraphs, so Markdown formatting isn't converted. Each Crumb item links to one ticket.
Setup
Crumb Cloud: connect Jira in one click from Settings → Integrations, on the Team plan and up. Issue creation, AI drafts and status sync all work as soon as you're connected: Crumb registers a status webhook on your Jira site for you and keeps it renewed.
Self-hosted: register an OAuth 2.0 (3LO) app in the Atlassian developer console with the scopes read:jira-work, write:jira-work, read:jira-user, and offline_access, point its callback at /api/integrations/jira/callback on your Crumb domain, and set JIRA_CLIENT_ID and JIRA_CLIENT_SECRET. For status sync, add a webhook in Jira's system settings for issue updates, pointed at /api/integrations/jira/webhook and signed with the secret you set as JIRA_WEBHOOK_SECRET. Settings → Integrations shows the exact URLs. AI drafting is a Cloud feature, so self-hosted tickets start from the feedback text. See the self-host guide.
Also works with Linear and GitHub
The same push-and-sync flow works with Linear and GitHub. A workspace can connect all three and pick the tracker each time it creates a ticket.
Frequently asked questions
Does the Jira integration work with Jira Server or Data Center?
No. Crumb connects through Atlassian's cloud API, so it works with Jira Cloud sites only.
Can I connect more than one Jira site?
Not today. A workspace connects to one site, the first one your Atlassian account can access when you authorize Crumb. You pick the project each time you create an issue.
Which issue type does Crumb create?
Task. The issue type isn't configurable yet, so switch it in Jira after creation if you need a Bug or a Story.
Does closing the Jira issue notify the customer?
Not by itself. Jira's status updates the Engineering field on the Crumb item, and someone on your team moves the item to Shipped. That status change is what emails the customer who sent the feedback through the widget.
Who writes the Jira issue?
You do, starting from the customer's own words. On Crumb Cloud's Team plan and up, Suggest with AI drafts a title and body that match your recent Jira issues, and you edit it before it's sent.