The two integrations most teams set up first: one so developers see bugs where they plan their work, and one so the team hears about what's happening without watching the inbox.
JIRA, Linear, GitHub, GitLab, ClickUp, Asana, Trello, Azure DevOps, Shortcut, Notion, Awork and Plutio all work the same way, with different names for the same things.
Connect the account, then say where tickets should land. JIRA wants a project and an issue type; Linear wants a team; Trello and Asana want a board and a list or section. Nothing will save until that destination is set — which is the usual reason a half-finished integration doesn't stick.
Then decide what to send. The switch sends matching tickets automatically; the picker next to it chooses which ticket types count. Bugs and crashes, usually — not questions.
The created task carries what Gleap collected: the description, and the technical detail that came with the report — which is the entire point. A bug report that arrives with the console log and the replay attached is one nobody has to reproduce blind.
Updates can travel in both directions: a task being updated, closed or commented on can come back to the Gleap ticket, so the person who reported it can be told without a developer having to remember who that was.
You don't have to automate it. With the integration connected, any ticket can be pushed from the ticket itself — which suits teams whose tracker is for confirmed work rather than for everything a customer reports.
Both post into a channel you choose. Slack can post a message per event, keep the conversation in a thread, and tell you when a ticket's assignee changes.
Threads are the setting worth getting right: one thread per ticket keeps a channel readable, where a message per update turns it into noise nobody follows.
Send to a channel the right people already read, not a new one created for the integration. And connect it more than once if the audiences differ — bugs to the engineering channel, feature requests to the product one — rather than sending everything to one place and asking people to filter.
Check the ticket type first: a ticket whose type isn't in the picker was never meant to be sent. Then check the destination still exists — an archived Slack channel or a deleted Jira project fails quietly, and reconnecting won't help until you point it somewhere real.
