Ticket Intelligence

Connect your GitHub Issues (Jira and Linear coming soon) and Mapnostics adds AI-powered effort estimates, impacted file predictions, and similar past fixes — directly on each ticket, in real time.

How it works

When you open a ticket in Mapnostics's Ticket Intelligence view, the AI reads the ticket title and body, searches your repository's codebase for related files and functions, and cross-references your git history for similar past issues. All without any manual tagging or labeling.

Effort estimation — AI reads the ticket and the affected code to estimate hours.
File impact — which files are most likely to be touched during this fix.
Similar past fixes — tickets from git history that involved the same files or symptoms.
Risk level — how dangerous the change is based on the blast radius of the affected code.

Live demo

Watch Ticket Intelligence analyse a real bug report — from idle to full AI analysis with effort estimate, affected files, and past similar fixes. Window height stays fixed throughout.

mapnostics.com/repo/mapnostics-app/tickets

Ticket Intelligence

AI-powered estimates, file impact, and similar past fixes

● LIVE

bugOpen#7

Dead code detection showing unexpected error on analysis

Running dead code scan on a repo with >500 files causes a timeout. Repro: connect any large repo and click "Analyze". Expected: scan completes. Actual: 504 timeout after 30s.

AI is analysing the ticket…

Effort Estimate2.5h

FILES LIKELY AFFECTED · 0

src/services/dead-code.service.tsHIGH

src/controllers/analyze.controller.tsMEDIUM

src/lib/batch-processor.tsLOW

SIMILAR PAST FIXES

→ Zombie scan timeout on 300+ files — fixed in #42

→ Analysis hanging on monorepos — fixed in #38

Effort estimates

How estimates are calculated

The AI reads the ticket description, identifies the likely affected functions and files using the codebase map, and estimates effort based on:

File count and size of likely-affected code.
Complexity of the affected functions (cyclomatic complexity).
Historical effort from similar past tickets in the same files.
Blast radius — how many other files depend on the affected code.

Accuracy

Effort estimates improve over time as Mapnostics learns from your team's actual cycle times. Estimates are calibrated to a senior engineer working alone — adjust up for junior engineers or unfamiliar areas.

NOTE

Effort estimates are advisory only. Use them for sprint planning and sizing conversations — not as performance metrics or commitments.

Ticket sources

GitHub Issues — fully supported. Connect under Settings → Integrations.
Jira — coming soon. Join the waitlist in the dashboard.
Linear — coming soon.
Azure DevOps — coming soon.

TIP

Even without a formal ticketing system, you can paste any text description into the Ticket Intelligence search bar and get an instant AI analysis — useful for Slack messages, emails, or informal bug reports.