Jira's Issue Collector is free. Its reports are plain text.
That costs you time.
It captures only what the reporter types. No screenshots, no console errors, no network logs. Every ticket arrives as a wall of text you have to decode.
Still supported — just still basic. Atlassian renamed the Issue Collector to the work item collector; it is not deprecated. But it remains text-first, has no built-in screenshots or console logs, and is available in company-managed projects only. Full answers below.
Jira Issue Collector example: what you set up and what you get
The work item collector lives under Project settings in a company-managed project. You pick a work type, choose a template, and Jira hands you a script tag.
<script type="text/javascript" src="https://your-site.atlassian.net/s/.../com.atlassian.jira.collector.plugin.jira-issue-collector-plugin:issuecollector.js?collectorId=abc123"> </script>
A visitor clicks the trigger, fills in a summary and description, and Jira creates a work item with exactly that text. A typical result:
That is the whole payload. No page URL, no browser, no screenshot, no console error, and the first reply is a question back to the reporter. The rest of this page is about the gap between this and a report a developer can act on.
What the collector does not give you
Here's what you're dealing with.
"Can You Show Me What You're Seeing?"
User reports: "The button doesn't work." Which button? What screen? What happens when they click it? You email them back. They respond 2 days later. Still no screenshot.
"What Browser? What Page? What Error?"
The ticket says "it's broken." No URL. No browser info. No error message. You spend 20 minutes trying to reproduce something you can't find because you don't know where to look.
"I Have to Triage All of This Myself"
Every ticket arrives with the same priority: none. You read each one, guess urgency, assign a category, set priority. That's 5 minutes per ticket before you even start working.
Same Jira, more context
IssueCapture sends tickets directly to your existing Jira—with context attached
What IssueCapture adds
Screenshots, context and AI triage, all in one lightweight widget
Screenshot Capture
One-click screenshot with annotation tools. Users circle the problem instead of describing it.
Console Error Capture
JavaScript errors captured automatically. Debug issues without asking "can you open DevTools?"
Network Request Logs
Failed API calls and slow requests logged. See exactly what went wrong.
AI Categorization
Tickets arrive pre-categorized. Bug vs feature request vs question—sorted automatically.
AI Priority
Urgency detected from content. "Site is down" gets flagged Critical automatically.
Duplicate Detection
10 users report the same bug? AI links them together. Fix once, close all.
Domain Allowlist
Only your approved domains can submit. No spam, no abuse.
User Pre-fill
Pass logged-in user info to the widget. No "who are you?" in every ticket.
Lightweight
31KB initial load. Screenshot adds 10KB. Won't slow down your site.
The same bug, two ways
What lands in your Jira depends on how it was captured
Your Jira stays as it is. IssueCapture is the form in front of it.
Issues flow directly into your existing Jira projects—with context attached.
Connect Your Jira
OAuth login. Select your project. Pick issue type. Done.
Add Widget to Site
One script tag. Same as the Issue Collector—but better.
Issues Arrive in Jira
Same project. Same workflow. Better tickets.
Pricing
Each follow-up email to clarify a ticket costs you time.
- Screenshot + annotation on every issue
- Console errors + network logs captured
- AI triage (priority, category, duplicates)
- Unlimited team members
- Direct Jira Software + JSM integration
Jira Issue Collector: Common Questions
Straight answers about where the Issue Collector stands today.
Did Jira replace the Issue Collector?
No — Atlassian renamed it. What used to be called the Issue Collector is now the “work item collector” in Jira Cloud, part of Atlassian's rename of “issues” to “work items.” It is still available and supported, but it was never upgraded: no built-in screenshots, no console or network logs, and it only works in company-managed projects. If you came looking for those capabilities, that gap is exactly what IssueCapture fills.
Is the Jira Issue Collector being deprecated?
Not as of 2026. Atlassian still documents and supports the work item collector (formerly the Issue Collector), with no end-of-life notice. The catch is not that it is going away — it is that it stays basic: text-first submissions, company-managed projects only, and no screenshots, logs, or AI triage.
Does the Jira Issue Collector work with team-managed projects?
No. Atlassian’s documentation states the work item collector is only available in company-managed spaces and is not available in team-managed spaces. IssueCapture works with any Jira project — company-managed, team-managed, and Jira Service Management.
How do I set up the Jira Issue Collector?
In a company-managed project, open Project settings, choose Issue collectors (labelled “Work item collectors” in newer Jira Cloud), click Add, pick the work type and a template (Feedback, Got feedback?, or Custom), copy the generated script tag, and paste it before the closing body tag of your site. Each submission creates a work item in that project with the text the reporter typed.
What is the best alternative to the Jira Issue Collector?
IssueCapture is a drop-in upgrade with the same one-script-tag embed, but every report arrives with an annotated screenshot, console errors, network logs, and browser and URL context — then AI triages priority, category, and duplicates. Issues flow straight into your existing Jira, including team-managed projects and JSM, so you keep your workflow and just get better tickets.
Get reports with the context already attached
Stop asking for more details. Screenshots, console logs, network context—all captured automatically. Issues arrive ready to fix.
- Works with Jira Software + JSM
- Same embed pattern you know
- Setup in 5 minutes