Forms

Build a public form anyone can fill in without an account; every response becomes an issue.

Forms

A form is a public page that anybody can fill in without an account — for bug reports, requests or feedback from people outside your team. Every response becomes an issue in the project you choose.

Create a form

  1. Choose Forms in the sidebar.
  2. Type a name in What are you asking people for? and choose the project responses should go to.
  3. Choose New form. The form builder opens.

The Forms page lists each form with its project, number of questions and responses, and whether it is Live or a Draft.

Add questions

On the Questions tab, choose Add question or Add section. Click a question to edit its title, type and options. Question types:

  • Text: Short answer, Paragraph, Number
  • Choice: Multiple choice, Checkboxes, Dropdown, Yes / no checkbox
  • Scale: Linear scale (with optional labels for each end), Rating
  • Date and time: Date, Time
  • Contact: Email address, Phone number, Website link
  • Layout: Section heading, to split a long form into parts

Each question can be Required, have a description (Add description), and be moved, dragged into a new order, duplicated or deleted. Choice questions can offer an Other… option. Changes save on their own about a second after you stop; the header shows All changes saved when they have.

A form holds up to 30 questions, and a choice question up to 40 options. A choice question needs at least one option before it can be saved.

Decide what each answer becomes

Each question has a Becomes setting that controls where its answer lands on the issue:

  • Just an answer — goes into the issue description along with the other answers.
  • The issue title — this answer becomes the issue's title. Only one question can be this. If no question is the title, the issue is named after the form.
  • Who sent it — for Email address questions only. The address is kept with the response so somebody can reply.

On the Settings tab, under Where responses go, choose the Project and what each response is Created as (Task, Bug, Story or Epic). Under After somebody submits, write the thank-you message they see (up to 500 characters).

  1. Check the Preview tab. It is exactly what a visitor sees; submitting there sends nothing.
  2. Choose Publish. The form needs at least one question.
  3. Use Copy or Open next to the link to share it. The link has the form /public/forms/<token> and works for anybody who has it, without signing in.

Until a form is published, its link shows This form isn't available. Unpublish stops accepting responses; publishing again reuses the same link. New link replaces the link immediately — the old one stops working, even for someone part-way through — while the form stays live.

Anybody with the link can submit. Share it only where you want responses from, and use New link if it spreads further than you meant.

What happens to a response

Each submission creates an issue in the form's project, of the type you chose. The answers are written into the issue description, each under its question's title. The issue gets the project's default status, assignment rules and automation like any other issue.

If the project uses triage, form responses always arrive in its triage inbox first, so someone can accept, decline or snooze them before they reach the backlog.

The person submitting sees only your thank-you message (or Thanks — that has been sent.) and can choose Submit another response. They are not told the project, the issue key or who will see it.

Review responses

The Responses tab shows every response, with a Summary view across all of them and an Individual view of each one, including the issue it became. Choose Download CSV to export them.

If a response's issue is in a project you cannot see, the response is still shown but without its issue link. Deleting a form deletes its questions and responses; the issues the responses created are kept.

Who can use forms

  • Anyone whose role can view projects can see forms and their responses. Guests cannot.
  • Creating, editing, publishing and deleting forms needs permission to manage projects.