Send it where the work already happens
Nine integrations. The tracker your engineers already live in gets the issue with the report inside it, and the status stays true on both sides.
Slack and Microsoft Teams on every plan · the seven trackers on Pro
Discount code accepted but total unchanged
Status
Priority
Severity
Assignee
Labels
checkoutIssues
The nine
-
Jira
Issue sync, two-way status
Pro
-
Linear
Issue sync, two-way status
Pro
-
GitHub
Issue sync, two-way status
Pro
-
Trello
Card sync, two-way status
Pro
-
Asana
Task sync, two-way status
Pro
-
ClickUp
Task sync, two-way status
Pro
-
monday.com
Item sync, two-way status
Pro
-
Slack
Channel notifications
All plans
-
Microsoft Teams
Channel notifications
All plans
How it works
1
Connect the workspace
Authorize the tracker once per project. Slack connects over OAuth; Microsoft Teams takes the URL of a Power Automate workflow that posts into a channel.
2
Map states to your pipeline
Connecting suggests a mapping — the provider's open, in progress and completed states against your first active, last active and first completed status — and you adjust it. A status left unmapped simply does not sync.
3
Link a ticket
Linking creates the issue or attaches an existing one, and the two stay in step from then on. Unlinking leaves the issue alone.
Engineering never leaves the tracker
This is what leaves for Linear when a ticket is linked: the reporter's own sentence, then the ticket id linking back to the board, who sent it, the page it broke on, the priority and severity your team set, and signed links to the screenshot and the recording.
It is written once, at creation, and never re-synced — so the thread an engineer builds under it is never overwritten by us.
Linear issueCreate(input: IssueCreateInput!) - title
- Discount code accepted but total unchanged
- priority
- 2 high
- teamId
- 6b0f2c19-4a7d-4e13-9c88-51ad03f7e6b2
- stateId
- c74e91a0-8d52-4fb6-a03e-2f19c6b845d7
description
The code applies but the order total never changes. I tried three codes. --- **Notarus ticket:** [NT-248](https://app.notarus.ai/p/9d31a6f4-70c2-4b58-8e0d-1a4f37c5be91/board?t=NT-248) **Reporter:** marta.ruiz@example.com **Page:** https://shop.example.com/checkout?step=payment **Priority:** high **Severity:** medium **Screenshot:** https://app.notarus.ai/s/8Qk2rTfx1pLm.jpg **Video:** https://app.notarus.ai/v/4Zt9wBnc7dRe.webm
Status stops being copied by hand
Each of your statuses maps to one provider state, and no two may share one. Connecting suggests the mapping and you own it from there.
A move on the board moves the issue, and a state change in the tracker moves the ticket through the same path a person on the board uses, so it lands on the activity trail with the provider's name on it. A status left unmapped does not sync rather than guessing.
Slack 
Microsoft Teams Linear 
Jira 
GitHub 
Trello Linear
Two-way issue sync with your Linear workflow.
Status mapping
Each Notarus status maps to one Linear state, and no two may share one — an unmapped status simply doesn’t sync.
Exact behaviour
- Trackers
- Jira, Linear, GitHub, Trello, Asana, ClickUp, monday.com
- Chat
- Slack and Microsoft Teams
- Direction
- Two-way status, through a provider-state mapping you own
- Evidence
- In the issue body at creation: the backlink, the reporter, the page, and signed screenshot and recording links
- Plan
- Chat on Free and Pro · the seven trackers on Pro
- MCP tool
- link_ticket_to_issue · sync_ticket · configure_integration · list_integration_connections · set_chat_destination
Questions teams ask before connecting
Which integrations are on the Free plan?
Slack and Microsoft Teams notifications are on every plan. The seven trackers — Jira, Linear, GitHub, Trello, Asana, ClickUp and monday.com — are a Pro capability.
Does a status change in the tracker move the Notarus ticket?
Yes. A connection stores a mapping between the provider's states and your own statuses, and the inbound half applies the provider's move through the same path a person on the board uses, so it lands on the ticket's activity trail.
What exactly ends up in the issue?
The reporter's own words, then the facts: the ticket id linking back to the board, who sent it, the page it happened on, and signed links to the screenshot and the recording. Jira and GitHub also take the browser, the OS, the viewport and the captured console and network lines. It is written once, when the issue is created, so nothing later overwrites what your team wrote underneath.
What happens to the issue when I unlink a ticket?
Nothing. Unlinking drops the link on our side and leaves the issue, its comments and its state exactly where they are.
Send your next bug report straight to the tracker.
Slack and Microsoft Teams are on the Free plan; the seven trackers come with Pro.