Bugsee integrations
Bugsee integrates with most bug trackers, project management and collaboration tools available on the market.
For each new issue created within Bugsee, a corresponding item can be created within your tool of choice (the item might be an issue, a card, a task, a chat message depending on the type of the tool on the receiving end). The resulting item will have a direct link to a Bugsee player for that specific issue. You have an option to create the items automatically as soon as new issue appear within Bugsee, or to push individual issues manually from Bugsee to your tool of choice.
Integrations come in two flavours, and which one you get is decided by the tool on the receiving end:
- Issue-based — Bugsee creates an item in the remote tool for a Bugsee issue, then keeps it up to date and mirrors comments onto it. This covers the bug trackers, the help desks, and the data-forwarding services: Datadog and Splunk are driven through the same issue flow, they simply receive an event or a log entry instead of a ticket.
- Event-based — Bugsee posts a message when something happens, with nothing to keep in sync afterwards. Only Slack and Microsoft Teams work this way. You choose which events are worth a message per application; see event-based recipes for the full list.
If you don't find your tool among the available integrations, please contact support@bugsee.com and we will be happy to explore the option of adding it.
Available integrations
Bug tracker and task management tools
- Aha!
- Asana
- Azure DevOps
- Basecamp
- BugHerd
- Bugzilla
- ClickUp
- GitHub
- GitLab
- HubSpot
- Jira
- Linear
- MantisBT
- monday.com
- Notion
- Nozbe
- Odoo
- Redmine
- Shortcut
- TargetProcess
- Teamwork Projects
- Trello
- Visual Studio Team Services
- Wrike
- YouTrack
- Zoho Projects
Messengers
Help desk tools
Data forwarding
What each integration can do
Create means Bugsee creates an item when an issue is pushed. Update means later changes to the Bugsee issue — state, summary, description, labels, priority — are mirrored onto that item. Comment means comments added in Bugsee are posted onto it. Notify means the integration receives event messages rather than items. Authentication lists the methods offered when setting the integration up.
| Integration | Create | Update | Comment | Notify | Authentication |
|---|---|---|---|---|---|
| Aha! | ✓ | ✓ | ✓ | — | Basic, Personal token, OAuth |
| Asana | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| Azure DevOps | ✓ | ✓ | ✓ | — | Personal token |
| Basecamp | ✓ | ✓ | ✓ | — | OAuth |
| BugHerd | ✓ | ✓ 1 | ✓ | — | Personal token |
| Bugzilla | ✓ | ✓ 2 | ✓ | — | Basic |
| ClickUp | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| Datadog | ✓ | — 3 | ✓ | — | Personal token |
| Freshdesk | ✓ | ✓ | ✓ | — | Basic, Personal token |
| GitHub | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| GitLab | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| HubSpot | ✓ | ✓ | ✓ | — | OAuth |
| iTop | ✓ | ✓ 4 | ✓ | — | Basic, Personal token |
| Jira | ✓ | ✓ | ✓ | — | Basic, Personal token, OAuth |
| Linear | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| MantisBT | ✓ | ✓ | ✓ | — | Personal token |
| Microsoft Teams | — | — | — | ✓ | OAuth |
| monday.com | ✓ | Partial 5 | ✓ | — | Personal token |
| Notion | ✓ | ✓ | ✓ | — | OAuth |
| Nozbe | ✓ | Partial 6 | ✓ | — | OAuth |
| Odoo | ✓ | ✓ 7 | ✓ | — | Basic |
| Redmine | ✓ | ✓ 7 | ✓ | — | Basic, Personal token |
| Shortcut | ✓ | ✓ | ✓ | — | Personal token |
| Slack | — | — | — | ✓ | OAuth |
| Splunk | ✓ | — 8 | — | — | Personal token |
| TargetProcess | ✓ | ✓ | ✓ | — | Basic, Personal token |
| Teamwork Projects | ✓ | ✓ | ✓ | — | Personal token |
| Trello | ✓ | ✓ 9 | ✓ | — | Personal token |
| Visual Studio Team Services | ✓ | ✓ 10 | ✓ | — | Personal token |
| Wrike | ✓ | ✓ | ✓ | — | Personal token, OAuth |
| YouTrack | ✓ | ✓ | ✓ | — | Personal token |
| Zendesk | ✓ | ✓ | ✓ | — | OAuth |
| Zoho Desk | ✓ | ✓ | ✓ | — | OAuth |
| Zoho Projects | ✓ | ✓ | ✓ | — | Personal token |
- BugHerd has no separate title field — the summary and description are stored as one body, so editing either rewrites the whole thing.
- Bugzilla cannot update a description after creation, and labels only sync if they already exist as administrator-defined Bugzilla keywords.
- Datadog receives an event per pushed issue. Later changes to the Bugsee issue are not mirrored.
- iTop only mirrors closing, and does so on a best-effort basis — a ticket that cannot take the transition keeps its state while the rest of the edit still applies.
- monday.com mirrors the item name and status only. Description, priority and label changes are not sent.
- Nozbe mirrors state and summary only. Because a Nozbe task has no description field, the Bugsee description is posted as a comment on the task.
- Odoo and Redmine do not sync priority; Redmine does not sync labels.
- Splunk receives an event through the HTTP Event Collector, which returns no id, so there is nothing to update or comment on afterwards.
- Trello has no status field — closing a Bugsee issue archives the card.
- Visual Studio Team Services shares its implementation with Azure DevOps, adapted for VSTS-era hosts and on-premise Azure DevOps Server. Comments are appended to the work item's history.