Backref
- 6 users
- No ratings yet
- #22,212in Developer Tools
Turn bug-tracker IDs in GitHub code comments, PR/issue descriptions and comments, and commit messages into clickable links.
by Alessio Bazzica · 1 listing
- Users
- 6
- #22,212 of 31,410 in category
- Rating
- —
- No ratings yet · median 4.63
- Version
- 0.2.0
- 2.05 MiB · Manifest V3
- Access
- Low17/100
- 2 permissions + 1 site pattern
Description
As written by the publisher on the storeBackref turns bug-tracker IDs scattered across GitHub into clickable links straight to your issue tracker. No more copy-pasting an ID into Linear, Jira, or your internal tool — every reference becomes a one-click jump.
- WHAT GETS LINKED
- Code comments (line and block)
- PR and issue descriptions
- Conversation and inline review comments
- Commit titles and bodies
- Already-linked text is left alone
HOW IT WORKS
Define rules in the options page — each rule is a regular expression plus a link template. The regex `\b[A-Z]+-[0-9]+\b` paired with the template `https://linear.app/your-org/issue/{id}/` turns every "BUG-123" on the page into a Linear ticket link.
You can add as many rules as you like, and each rule can be scoped to specific hosts — so you can link Linear IDs on GitHub, Zendesk IDs on Linear, and anything else you want, all from one extension.
- WHY INSTALL
- Faster context switching between code and tickets — the link is always there, no manual searching.
- Works alongside AI tools: when your AI assistant leaves comments like "// TODO(BUG-123)", those references become instantly navigable for both humans and the next AI session that needs ticket context.
- Self-hosted GitHub Enterprise and other Git forges work too — just add the host in settings.
PRIVACY
Backref runs entirely in your browser. It does not send any data anywhere — your configuration and the page contents stay local. The source is open at https://github.com/alessiob-riverside/backref.
FOR ORGANIZATIONS
Backref supports Chrome Enterprise managed storage. IT pushes the regex and tracker URL once via policy, and every employee gets the same setup with zero manual configuration. Per-rule host scoping and lock flags are supported.
Ratings and reviews
Ratings as the store shows themNo written reviews held for this listing yet.
Track Backref on Radar
This page shows the listing as it is today. Add it to Radar and get one email when it changes.
- Users and rating
- Store text and screenshots
- Permissions it asks for

Backref, in plain words
What it is, what to use instead, what it can access and how to fix it.
Backref at a glance
Backref is a Developer Tools extension by Alessio Bazzica with 6 users. It has no store ratings yet, so there is little public feedback to go on. By users it sits in the lower half of Developer Tools extensions.
- By users
- #22,212of 31,410 in Developer Tools
- Access
- Low17 of 100
Backref alternatives
Closest by what they do · users as the store shows them · bars on a log scaleIs Backref safe?
Backref asks for 2 permissions and access to 1 site pattern. None of them are on our list of wide-access permissions.
Permissions show what it could do, not what it does. See the full permission list.
storageNot on our wide-access listscriptingNot on our wide-access list
Every permission Backref asks for
2 permissions + 1 site pattern · none sensitive · Low access overallSites
- Read and change data on matching sites
*://github.com/*
Browser permissions · 2
- Save its own settings
storage - Run its code on pages it can access
scripting
Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.
Backref not working?
What recent reviews say
Store reviews from the last 90 daysWe have no recent public signals of problems with Backref.
Common fixes
Try them in this order- 1Update Chrome and the extension
- 2Turn it off and on in chrome://extensions
- 3Reload the page
- 4Turn other extensions off in case two clash
Still stuck? Contact the maker or try an alternative.
Know when a listing changes
Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.