Skip to main content
All CollectionsWidgetConfiguration
Widget Form Configuration
Widget Form Configuration

Some advanced widget form configuration advice

Joe Scanlon avatar
Written by Joe Scanlon
Updated over a week ago


This guide offers an in-depth look at configuring widget forms in, tailored for specific users, whether internal to your team or external clients/stakeholders. We explore features like prefix usage, default value settings, and mandatory field support, providing a clear understanding of how you can enhance your feedback process.

Understanding Form Types

Widget forms in are divided into two main categories: Guest Forms and Member Forms. Each is designed to cater to different user roles and technical proficiencies.

Learn more about our User Roles and collaboration process.

Guest Form

Guest forms are intended for Public Reporters and Guests, these forms are recommended to be kept simple to avoid overwhelming non-technical users.

Member Form

Member forms aimed at Members and Admins who are more technically savvy, these forms can be customized to be as detailed as required.

Advanced Form Configuration

Prefix in Form Entries

You can now add a prefix, a short piece of text, to the title of each feedback via the guest form.

Prefix Benefits:

  • Helps the sorting and categorization process in your tools.

  • Enhances the clarity and context of feedback submissions.

If you would like to have this functionality on the member form also, please vote here.

Field Mirroring

All fields within your forms are directly mirrored from your existing project management tools. This means if you're using fields like “Sprint” in Jira, custom fields in Asana, or “Milestone” fields in GitHub, these will be readily available and reflected in your forms.

Field value synchronization

Every time your forms are loaded in, field values from your issue tracker are instantly and automatically synchronized.

Add a new team member in Jira, Asana, or GitHub? They're immediately available in the assignee field on your forms.

In case of any rare delay, simply click the refresh button next to the field name for an immediate update.

This feature ensures that your forms are always current, reflecting the latest changes in your team and project management tools.

Field Visibility

Adapt your forms by hiding sensitive or irrelevant fields, ensuring only relevant information is collected. Fields in your forms mirror those in your issue tracker, allowing for precise control over what is displayed to reporters.

This feature ensures only key information is collected for more efficient and relevant information gathering.

Default Values & Preset values in Forms

Default values are pre-set answers or selections in form fields.

They help to:

  • Reduce repetitive entry.

  • Ensure consistency and accuracy in the data collected.

  • Speed up the form-filling process, especially for frequent or similar feedback submissions.

This feature is designed to make your form-filling experience quicker and more consistent.

For example, say you'd like to preassign all feedback from the current project to one person. Then preset that field, and hide it from your reporters as below.

Mandatory Fields

If your integration allows mandatory/required fields, these will be mapped accordingly to forms, and displayed with an asterisk * to signify that they are required. This helps with:

  • Enhanced Reporting Consistency: Ensuring that every reporter adheres to a uniform reporting standard.

  • Critical data: Ensures no important details are overlooked in the reporting process.

  • Improved Report Quality: The consistency helps the overall quality of reports.

  • Efficient Issue Tracking: A standardized format helps faster resolution of problems.

You may choose to either display the required field to the reporter, or preset the field and hide it from the reporter.

Map data to existing fields in your integration.

Often, teams want to customize their workflow by adding specific data collected by into fields within their tools.

For example:

  • Map the reporter's email address to a specific field in Jira

  • Link the browser version to a field

  • Capture additional custom data and place it in a field in my tools

While this feature is not currently available, please do consider voting on it here and adding your own context. Every vote and comment helps convince our team to build out each feature. 🙏

Did this answer your question?