logoTskVlo
Download
How-To Guides
boards 6 min read

Collecting Requests with Public Forms

Create a public form for a board, choose which fields to ask for, add conditional questions, and share the form by link or embed it on your website.

Public forms let people outside your workspace — clients, customers, colleagues from other teams — submit requests straight into a board. Every submission becomes a new item in the group you choose, with the answers already in the right fields.

Before You Start

  • Only workspace owners and admins can create and manage forms. Other members see an “Admin access required” notice on the Forms page.
  • Forms are built from the board’s fields, so set up the fields you want to ask for first (see custom fields). Text, number, status, date, date range, checkbox, tags, URL, rating, and progress fields can be used; person and formula fields are not offered.
  • Decide which group new submissions should land in — a dedicated group such as Inbox or New Requests makes triage easy.

Creating a Form

  1. Open the board and go to Board Settings → Forms.
  2. Click New form.
  3. Enter a Title — it’s shown at the top of the public form.
  4. Pick the Target group for new submissions.
  5. Optionally add a Description telling submitters what information to provide.
  6. Adjust the Submit button text and the Success message if you don’t want the defaults (“Submit” and “Thanks! Your request has been submitted.”).
  7. Leave Active checked so the form accepts submissions right away.

Choosing the Questions

The left column lists the board’s fields. Check each field you want to ask for — it appears as a question in the right column. For every question you can:

  • Edit the Question label, e.g. turn a field called Due into “When do you need this by?”
  • Tick Required so the form can’t be sent without an answer
  • Add a Placeholder as helper text inside the input

Questions use the input that matches their field type: a dropdown for status fields, a date picker for date fields, stars for rating fields, a slider for progress fields, and so on. A form needs at least one question before it can be saved.

Showing Questions Conditionally

Any question except the first can depend on an earlier one:

  1. In the question’s settings, open Show only after and pick an earlier question (the default is Always show).
  2. Enter the Equals value the earlier answer has to match.

The question only appears once the earlier answer matches that value exactly. Hidden questions are skipped on submit — even if they’re marked as required — so submitters only fill in what applies to them. Conditions work best with questions where the submitter types the answer, such as text or number fields.

Click Save when the form is ready.

Each form in the list shows its target group and number of questions. Click Copy to copy the form’s public link, or the external-link icon to open it in a new tab. Anyone with the link can fill out the form — no TskVlo account needed.

Embedding the Form on Your Website

  1. Expand the form in the list to show its details.
  2. Under Embed, click Copy script.
  3. Paste the snippet into your website’s HTML where the form should appear.

The snippet consists of a placeholder <div id="tskvlo-embed-form"> and a script tag that loads the form into it. The embedded form uses a transparent background, so it picks up your page’s design, and it resizes automatically as questions appear or the success message is shown. Adjust the div’s width to fit your layout.

What Happens on Submit

When someone sends the form, TskVlo:

  • Creates a new item in the form’s target group, titled after the form
  • Fills each answered question into its board field
  • Shows the submitter your success message

The new item shows up on the board for your team like any other item, ready to be triaged, assigned, and worked on.

Editing, Disabling, or Deleting a Form

  • Click Edit on a form to change its settings or questions. The public link and embed script stay the same.
  • Uncheck Active to pause a form. Its link and embed stop loading until you turn it back on; nothing is lost.
  • Delete a form when it’s no longer needed. This removes the form itself, not the items it already created.

Tips

  • Use one form per type of request and route each to its own group — bug reports to Bugs, feature ideas to Ideas.
  • Write question labels the way a submitter would phrase them, not the internal field names.
  • Keep forms short: mark only the essentials as required and use conditional questions for details that only matter sometimes.
  • If requests already arrive by email, board email intake is a second way to turn them into items.
← Back to Guides