This guide covers form types, field configuration, presets, required fields, issue types, priority, AI features, and dynamic variables.

Overview

Widget forms control what reporters see when they submit feedback through the Marker.io widget. You can configure which fields appear, set default values, rename labels, and use AI to simplify the experience — all without changing anything in your connected tools.

Feature	What it does
Guest & Member forms	Tailor form complexity to your audience
Field syncing	Fields and values pulled directly from your project tools
Show or hide fields	Control what reporters see
Required fields	Ensure critical information is always submitted
Default & preset values	Pre-fill answers to save time
Rename field labels	Make technical field names reporter-friendly
Title & prefix	Hide the title field with AI; add a prefix for categorisation
Issue Types	Let reporters choose Bug, Improvement, etc. — each with its own form
Issue Priority	Classify issues by urgency
AI features	Auto-generate titles, rewrite descriptions, translate feedback
Dynamic variables	Auto-inject reporter info, browser context, and custom data (Team plan+)

Choose your form type

Widget forms come in two types:

Guest Form — Used by Public Reporters and Guests. Keep these simple. Non-technical users shouldn't need to navigate complex fields just to report an issue.

Member Form — Used by Members and Admins. These users are more technically savvy, so you can add as many fields as you need.

Each form type is configured independently, and each Issue Type can have its own form layout — so a "Bug" report can ask different questions than an "Improvement" suggestion.

Show or hide fields

You can hide any field that is sensitive, irrelevant, or unnecessary for a given audience. Hidden fields still exist in your integration — they just won't appear on the form.

To configure field visibility: Dashboard → Website Project → Widget → Guest/Member Form.

Make fields required

If your integration has mandatory fields (e.g., "Priority" in Jira), Marker.io marks them with an asterisk (*) automatically. You have two options:

Show them to reporters and let them fill in the value.
Preset a default and hide the field, so reporters don't need to think about it.

You can also mark any field as required directly in Marker.io, even if your integration doesn't enforce it.

⚠️ If you hide a required field, always preset a value first. Otherwise, submissions will fail.

Set default and preset values

Default values are pre-filled answers in form fields. Use them to:

Reduce repetitive entry — stop filling in the same field on every submission.
Ensure consistency — every issue gets the same value unless a reporter changes it.
Speed up submissions — especially useful for frequent or similar reports.

You can preset a value and leave the field visible (reporter sees a suggestion but can change it) or preset and hide it (reporter never sees it, but the value is always set).

Examples:

Preset the Assignee to one person and hide it — every issue from this project goes to them automatically.
Preset Issue Type to "Bug" and hide it — all feedback is categorised without the reporter needing to choose.
Preset Priority to "Medium" — clients don't accidentally mark everything as urgent.

Rename field labels

You can rename any field label displayed on the widget without changing anything in your connected tool. This lets you translate technical field names into language your reporters understand.

Examples:

"Repro Steps" → "What happened?"
"Summary" → "Give your issue a short title"
"Issue Type" → "What kind of feedback is this?"

To edit labels: Dashboard → Website Project → Widget → Form → click the edit icon next to any field label. Changes are cosmetic — your integration's field names stay untouched.

Title, description, and prefix

Title field: Can be hidden when AI Title Generation is enabled. Reporters see only the description field, and Marker.io generates the title automatically when the issue is submitted.

Description field: Always visible. This is where reporters describe their feedback.

Prefix: You can add a short text prefix to the title of every issue submitted through a guest form. This helps with sorting and categorisation — for example, a prefix of "[Homepage]" means every issue appears as "[Homepage] Button not working" in your backlog.

💡 Prefix is currently available on guest forms only. Vote for member form prefix support →

Issue Types on forms

Issue Types let reporters choose what kind of feedback they're submitting — Bug, Improvement, Feature Request, or custom types you define. Each issue type can have its own form layout with different fields.

You can control which issue types are visible to guests versus members. If only one issue type is enabled, the selector hides automatically.

Full Issue Types documentation →

Issue Priority on forms

Issue Priority lets reporters — or you — mark how urgent feedback is. You can show the priority field to reporters, or preset it and hide it like any other field.

When a website project is connected to an integration, you may see your integration's native priority field instead of Marker.io's.

Full Issue Priority documentation →

AI-powered form features

Three AI features enhance the widget form experience:

AI Title Generation — Hide the title field entirely. Reporters write a description and Marker.io generates the title on submission.
AI Magic Rewrite — Reporters clean up rough descriptions into structured, actionable feedback with one click.
AI Translation — Reporters write in their native language (200+ supported). Marker.io translates the title and description into your team's language.

All AI features are in beta and free on all plans. Enable them under Website > Settings > AI.

Get started with AI features →

Dynamic variables

Dynamic variables let you auto-inject reporter info, browser context, and custom metadata directly into form fields. Use the {{variable}} syntax in any text-based field.

Examples: