Most teams connect two things first: an issue tracker, so developers see bug reports where they plan their work, and a chat tool, so the team hears about new tickets without watching the inbox. Only project admins can set this up, and it needs the Team plan or higher.
Jira is the example here. Linear, GitHub, GitLab, Azure DevOps, ClickUp, Asana, Trello, Shortcut, awork, Plutio and Notion work the same way.
Go to Settings → Connectors, pick the Integrations filter and click Add integration.
Pick Jira, click Connect with Jira, then sign in to Atlassian and approve access.
Open the Jira connection and click Send tickets.
Choose the Organization, the Project and the Issue type new issues should get.
Turn on Send tickets automatically. A Ticket types picker appears under it, with every type selected.
Untick every type that doesn't belong in Jira. Usually that leaves Bug.
Click Save.
From now on, every new ticket of those types becomes a Jira issue with the description and the technical detail that came with the report, such as console logs and the replay link. Gleap keeps the ticket's status in sync with the issue, so nobody has to watch both systems.
The same group has Mark as done when sent, Send duplicates, Don't send personal data and Don't send internal notes. Save stays off until the destination is set, which is the usual reason a half-finished integration doesn't stick.
Tool | Where new tickets land |
|---|---|
Jira | Organization, Project, Issue type |
Linear | Team, Project (optional) |
GitHub | Repositories |
ClickUp | Team, Space, Folder (optional), List |
Asana | Workspace, Projects, List |
Trello | Project, List |
You don't have to automate it. Leave Send tickets automatically off, open a ticket and click Send to integration in the Integrations section of the ticket sidebar. With Forward new comments on, later comments on tickets you sent by hand follow automatically. Many teams do both: automatic for bugs, by hand for everything else.
Go to Settings → Connectors, pick Integrations and click Add integration.
Pick Slack, click Connect with Slack and allow the Gleap app in your workspace.
Open the Slack connection, click Notifications and pick the Channel. Private channels show up once the Gleap app is added to them in Slack.
Choose which Ticket types are posted, then click Save.
Each ticket's updates go into its own thread, which keeps the channel readable. Turn on 2-way sync and replies in the Slack thread are synced back to the ticket. Discord and Microsoft Teams post new tickets and replies the same way. Connect the tool more than once when audiences differ, such as bugs to the engineering channel and feature requests to the product one.
Check the ticket type first: a ticket whose type isn't selected under Ticket types is never 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 the integration somewhere real.
