Tracer is an issue tracker with an opinion. High and Urgent need a second pair of eyes before they count. Real production incidents skip the queue entirely. And the AI does the writing-up, so a pasted stack trace becomes a proper ticket in one click.
Free for your first project · No card required
GST missing on processing fee at cart
Credit not applied on checkout
Checkout 500s on discount codes with %
Ticket value not split for couple passes
Why another tracker
When anyone can mark anything Urgent, urgency stops meaning anything — and the genuinely broken things get lost in the noise.
Tighten the rules and you slow down the one case that actually can't wait: production is down, right now.
Bug reports arrive as a Slack message and a screenshot. Someone has to turn that into something a developer can act on.
Priority approval
When someone sets an issue to High or Urgent, it doesn't change yet. The issue keeps its current priority and shows as awaiting approval until a Lead signs off — so your dashboards stay honest and your urgent queue stays short.
GST missing on processing fee at cart
Requested: HIGH by Bhaskar — awaiting approval
Effective priority stays MEDIUM until approved
Incident fast lane
Approval is the right default — right up until production breaks at 2am and the one person awake isn't a Lead. Declaring an incident skips every gate: straight to Urgent, no approval, no sprint, visible to the whole team immediately.
Checkout 500s on discount codes containing %
AI assistance
Every suggestion is reviewable and editable before it's applied — nothing is written to your board without a person saying yes.
Paste a Slack message, a bug report or a raw stack trace. Tracer writes the title, description, type, priority and labels — you review and save.
Ask for a second opinion on any issue and get a suggested priority with the reasoning spelled out.
Catch up on a thirty-comment argument in a couple of sentences instead of reading all of it.
Everything else
Drag and drop across Backlog → To Do → In Progress → In Review → Done.
Plan with real start and end dates. One active sprint per project, with a backlog view.
Viewer, Member, Lead and Admin — scoped per project, enforced on every request.
Attach images straight to an issue. Bug reports that show, not just tell.
Every status, priority, assignment and approval change, recorded automatically.
Open, urgent, unassigned and closed-this-week, rolled up across everything.
Search, priority, assignee, sprint, and an incidents-only toggle.
The board stacks, the nav collapses. Triage from anywhere.
Getting started
Sign up with your work email. You get a private workspace for your company — your projects, your people, your data, isolated from everyone else's.
It arrives ready to use: Bug, Task, Story and Epic types, a Backlog → Done workflow, and a board waiting for its first issue.
Add teammates and give each one a role — Viewer to read, Member to work, Lead to approve priorities and run sprints, Admin to manage everyone.
Paste a bug report and let the AI draft it, attach a screenshot, set a priority. If it's genuinely on fire, declare an incident and skip the queue.
Pricing
Everything in Tracer works on the free plan — the boards, the AI, the approvals, the incidents. The only limit is how many projects you run.
For one team finding its feet.
₹0
For teams running more than one thing at a time.
Custom
Questions
Yes. Every organisation gets its own isolated workspace — projects, issues, people and attachments are scoped to it, and enforced on every single request, not just in the interface.
Anyone with the Lead or Admin role on that project. You decide who those people are, and it can be different per project.
Declare it an incident. It goes straight to Urgent with no approval step and no sprint, and shows up immediately in the incidents view for the whole team.
No. They're there when you want them and out of the way when you don't — nothing is written to an issue unless someone reviews and accepts it.
That's the free plan. One project, no card, no time limit. Move up when you need a second project.
Set up your workspace, add a project, and raise your first issue in the time it takes to write the bug report by hand.