A Linear issue for every submission
Bug reports, feature requests and support forms end as issues anyway. Skip the retyping: each submission opens a Linear issue in the team you pick, with a title and description you wrote and the answers in them, ready to triage.
Updated
How it works
- Open the form’s Integrations, pick Linear, and connect a Linear workspace or pick one already connected. Pick the team, and a project if every issue belongs to one.
- Write the title and the description. Type @ to insert an answer or the PDF link. The title is plain text up to 255 characters; the description is Markdown, with headings, lists, code blocks and links.
- Click Turn on Linear, then Send test to create a real issue with a
[Test]prefix, which you archive afterwards.
An issue a triager can read
Put what decides priority in the title: the severity, a one-line summary, the company. Keep the description for the steps, the environment and the files; a file upload shows its name and a download link. An empty title falls back to “New submission to” followed by the form’s name. A repeating group inserted with @ lists every entry, joined with “ · “.
When someone does not finish
On Pro and Business, a public-link response left unfinished for 12 hours, a day, three days or a week can open an issue of its own, labelled partial-submission, with a title and description written for that case. A request reminds the recipient instead.
When delivery fails
Deliveries are queued and tried up to five times. Formstep refreshes Linear tokens on its own; a revoked token, a lost permission or a deleted team stops the integration at once and emails the person who set it up. Reconnect or fix the cause, then Resume.
A form that reaches Linear often starts as a support request or a bug report; the templates have forms to adapt. GitHub Issues does the same for a repository, and Slack announces the issue to the channel.
