Jira Issue Collector: Setup Steps, Forms, and Examples 2026
Need a better way to capture bug reports? Learn Jira issue collector setup steps, form fields, and examples for 2026. Read now to get started.
Collecting bug reports through scattered emails and chat messages makes small problems harder to track. Important details go missing, reports arrive without clear steps to reproduce, and your team spends time copying them into Jira.
A Jira issue collector can place a feedback form on a website, helping visitors submit issues directly to a Jira project. But here's the truth: setup depends on your Jira edition, and older instructions may not match the options available in 2026.
I’ll walk you through the classic setup, show what to put in the form, and explain how to test it safely. You’ll also see examples for bug reports and feature requests, plus practical alternatives if the collector is unavailable in your environment.
How to set up a Jira issue collector
A Jira issue collector is an embeddable feedback form that lets people submit issues to a Jira project from a website. It can create a structured issue without asking visitors to open Jira first.
Before you start, check whether your Jira edition and current product lifecycle include issue collectors. Availability can differ across Jira products and versions, so confirm that the collector option appears in your project settings.
- Choose the destination project. Pick a project with a clear owner and a workflow suited to incoming feedback. Decide which issue type should receive submissions, such as Bug or Task.
- Open the collector settings. In Jira, check the project settings for an Issue collectors option. The exact menu labels can vary by edition and interface version.
- Create the collector. Give it a name that identifies its purpose, such as “Product site bug reports.” Select the issue type and configure any default values the project requires.
- Choose the form fields. Ask for the details your team needs to triage a report. For a bug form, that might include a short summary, steps to reproduce, browser, and impact.
- Set the display and trigger behavior. Choose when the form appears, how visitors open it, and which fields are required. Keep the initial form focused so people can finish it quickly.
- Preview and copy the embed code. Review the form, then copy the generated snippet. Add it to the appropriate page or website template using your normal release process.
- Submit a test issue. Test the form as a visitor, then confirm the new issue lands in the right project with the expected issue type, fields, and workflow.
Here’s why the final test matters: a form can look correct while submitting to the wrong project or failing because of permissions. Test from the same page and access conditions real visitors will use.

Choose fields that help your team act
A useful form asks for enough context to make a report actionable without making visitors fill out a lengthy questionnaire. Start with the minimum information your team needs to understand and route an issue.
Example fields for a bug report
- Summary: A short description, such as “Checkout button does not respond on mobile.”
- Steps to reproduce: A clear sequence, such as “Open the cart, select Pay, then tap Confirm.”
- Expected and actual result: Ask what the visitor expected and what happened instead.
- Environment: Request useful details like browser, device, and operating system.
- Impact: Let the visitor describe whether the issue blocks a task or affects one part of the experience.
- Contact details: Ask only if someone may need to follow up. Explain how the information will be used.
Keep optional fields optional unless they are essential for triage. For example, requiring a browser version may discourage a visitor who only knows that checkout failed on their phone.
Separate fields by purpose
Use Jira fields that match the work your team will do. A field for “Steps to reproduce” is more useful than a general prompt asking visitors to “Tell us more.”
For feature requests, replace technical questions with prompts about the task, the current workaround, and the outcome the visitor wants. That gives product teams more context than a bare “Please add this” request.
Examples: bug reports and feature requests
The same collector can support different feedback workflows, but one form rarely works equally well for every request. Align its questions and destination with the team expected to respond.
Example: report a website bug
A software company places a “Report a problem” link beside its help content. The form asks for a summary, steps to reproduce, browser, and optional contact details.
A report like “The save button stays gray after I add a valid address” gives a support or engineering team a useful starting point. The team can then confirm the behavior and request more information if needed.
Example: suggest a product improvement
A product team uses a feedback form on a feature page. It asks what the visitor was trying to do, what slowed them down, and how they handle the task today.
For instance, a visitor might explain that they export a report manually every Friday. That context helps the team assess the underlying need instead of treating each requested feature as an isolated vote.
The best part? A clear form can make submissions easier to compare. Keep the questions consistent, then use Jira fields and labels to help the team sort incoming issues.
Permissions, privacy, and website testing
Embedding a form does not remove the need to review Jira permissions. Confirm who can submit issues, which project receives them, and whether visitors can see any response or issue information afterward.
Anonymous issue creation can introduce unwanted submissions or expose more project access than intended. Have a Jira administrator review the relevant permission settings before allowing public submissions.
Protect visitor information
Ask only for information that helps resolve the report. Avoid requesting passwords, payment details, or other sensitive personal information in an open feedback form.
If you collect contact details, tell visitors why you need them and who may follow up. Coordinate the form wording with your organization’s privacy practices.
Test the embedded experience
Test the form on the actual page, on mobile and desktop, and in a browser session that matches a typical visitor. Check for layout problems, blocked scripts, and unexpected login prompts.
Also verify your website’s security settings. A content security policy, browser extension, or network rule may prevent an embedded form from loading even when the collector works inside Jira.
Troubleshoot common setup problems
If a collector does not behave as expected, start with the simplest checks: confirm the project, inspect the embed placement, and submit a fresh test issue. Then narrow down whether the problem comes from Jira permissions or the website.
The collector setting is missing
Check your Jira edition, version, and administrator settings. Feature availability can change over time, and a tutorial written for another deployment may show a menu your team does not have.
If the option is unavailable, do not build a launch plan around an older instruction. Ask your administrator which supported intake methods are available for your environment.
The form does not appear on the website
Verify that the embed snippet is present on the intended page and has not been altered by the site’s publishing system. Test with browser developer tools or ask your web team to check for blocked scripts and security restrictions.
Confirm that the page uses the correct address and that the visitor’s browser can reach your Jira environment. A form that works on an internal network may not load for people outside it.
Submissions fail or land in the wrong place
Recheck the collector’s project, issue type, required fields, and permissions. A mismatch between required Jira fields and the questions shown on the form can prevent successful submission.
Submit a test issue and inspect its field values and workflow status. If the issue is created but routed incorrectly, adjust the project configuration or automation rules and test again.
When a broader intake workflow may fit better
A website collector is useful when you need a simple route for external feedback. It may be less suitable when requests need approval, multiple review stages, or coordination across several teams.
You might be wondering: what if the collector is missing, or the team needs more than an embedded form? Consider a supported customer portal, a managed intake process, or a project workflow that your team can maintain.
For any alternative, test the visitor experience and the team’s handling process together. A clean form is only part of the solution; someone still needs to triage, assign, and resolve each request.
Website feedback workflow solution: ONES.com

Value proposition
ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for knowledge management. They are sold separately, so a team can choose the product that fits its workflow.
ONES Project is a Jira alternative for teams that need structured issue handling, configurable workflows, and project reporting. It is not an embedded Jira issue collector; consider it when your broader project process needs an alternative.
Core capabilities
- Incoming work lacks clear ownership: ONES Project workflows help define stages and responsibility, giving teams a consistent path from intake to resolution.
- Teams need fields that fit their requests: Custom fields let teams capture relevant details, such as request type or affected area, without relying on one generic description.
- Work moves through repeatable review steps: Custom workflows help map approvals and handoffs, making the status of a request easier to follow.
- Teams coordinate work in sprints: Sprint management supports planning and tracking work that needs to be delivered in time-boxed cycles.
- Managers need progress visibility: Built-in reporting gives teams a way to review work and monitor progress without assembling every update by hand.
- Repeated actions take unnecessary effort: Automation can handle routine workflow tasks, reducing manual updates when configured for the team’s process.
- Jira teams rely on many add-ons: Jira-compatible workflows and native capabilities can reduce plugin dependence for teams whose needs fit the platform.
- Deployment requirements vary: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Application scenarios
Product feedback triage: A product team can create a workflow for incoming suggestions, review them, and assign accepted work to a planning stage. Custom fields can capture the user need and affected product area.
Restricted-network project coordination: A team with on-premise or air-gapped requirements can manage project work in a deployment that fits its environment. ONES Wiki can be considered separately when the team also needs a knowledge base.
ONES.com offers a free plan for up to 30 seats. Compare its workflow and deployment options with your requirements before migrating; a project platform does not automatically replace a public-facing feedback form.
Common challenges and practical fixes
- Problem: Visitors abandon a long form. Fix: Remove questions that do not help initial triage. Make secondary details optional, and ask follow-up questions after a team reviews the issue.
- Problem: Reports arrive without enough detail. Fix: Use specific prompts and examples. “What did you expect to happen?” usually produces a clearer answer than “Add details.”
- Problem: Public submissions create noise. Fix: Review permissions, limit the information exposed, and assign someone to monitor incoming issues. Add moderation or spam controls if your website supports them.
- Problem: Staff cannot tell which requests need attention. Fix: Set clear ownership and triage rules. Use consistent issue types, fields, or workflow states to distinguish urgent bugs from general suggestions.
- Problem: An older tutorial does not match your Jira menus. Fix: Confirm the current product edition and feature availability with your administrator. Choose a currently supported intake method if the collector is unavailable.
FAQs
Does the Jira issue collector work with every Jira edition?
No. Availability can depend on the Jira product, version, deployment, and current feature lifecycle. A guide written for one edition may not match your settings, especially if the interface or feature availability has changed. Check your project settings and ask a Jira administrator before choosing the collector as a long-term intake method. If it is missing, explore an available portal or another supported workflow.
Can visitors submit a Jira issue without a Jira account?
That depends on the collector configuration and project permissions in your Jira environment. Public or anonymous issue creation can raise security and spam concerns, so an administrator should review access before you publish the form. Test the experience in a visitor session without a Jira login. Confirm both that a submission succeeds and that the visitor cannot view information they should not access.
What should I include in a bug-report form?
Start with a short summary, steps to reproduce, expected and actual results, and relevant browser or device details. Ask about impact if it helps your team prioritize the issue. Keep contact details optional unless follow-up is essential, and tell visitors why you are collecting them. A focused form usually gets more complete responses than a long form with questions unrelated to triage.
What can I use if the collector option is unavailable?
First check which intake options your Jira administrator supports. Depending on your environment, a customer portal, another approved form, or a managed project workflow may be more appropriate. Choose an option that securely routes submissions to the responsible team and supports follow-up. If you are considering a project platform such as ONES Project, assess it as a broader Jira alternative rather than assuming it replaces an embedded website form.
Conclusion
A Jira issue collector can route website feedback into a project through an embedded form, when the feature is available in your Jira environment. Start by confirming availability, then configure useful fields, review permissions, and test the visitor experience before publishing.
Keep the form short, give each submission a clear owner, and choose an intake method your team can support. If a collector is unavailable or your workflow needs more stages, compare supported alternatives against the process you actually need.