Give a known request a clear home.
Create work in a specific project. Collect a title and useful detail, with defaults for the work type, starting stage, assignees and labels.
Forms · A useful way in
Get the request.
Keep the context.
Ask the questions your team needs answered. Bring requests into a project or team, or collect feedback as Signals evidence, with the original response close at hand.
Creating new forms requires Starter or above. Explore plans
Tell us
what happened.
A feedback form with Signals as its destination.
WHAT DID YOU NOTICE? · REQUIRED
Describe the problem in your own words.
WHERE DID IT HAPPEN?
Add a page or source link.
ANYTHING ELSE WE SHOULD SEE?
Attach a screenshot or supporting file.
Original response Evidence for triage
Choose where the response belongs
Some requests are work.
Some need a closer look.
Choose the destination when you create the form. Each accepted response preserves its questions and answers alongside the resulting work or evidence.
Make intake part of the team's day.
Bring requests into an eligible Team's workflow. Map answers to the work item and keep the extra questions in its recorded context.
Gather the evidence before deciding.
Record feedback as raw evidence, with optional starting projects. Looper can group related reports and suggest work; your team reviews what to accept.
Explore SignalsAsk for the detail that matters
A better question.
A better starting point.
Build a form with text, choices, checkboxes, dates, numbers, email and website fields, plus file uploads. Add help text, mark required answers, and put the questions in a useful order.
Map compatible answers to a title, description, acceptance criteria, due date, severity or discovery timebox. Signals forms map report content and a source link.
- 1
Build and preview the draft.
Check the questions, introduction and confirmation message. Previewing helps you inspect the form without sending a response or creating work.
- 2
Publish when it is ready.
Respondents see the published version. Later edits stay in the draft until you publish again, and earlier answers retain the version they used.
- 3
Review what came back.
Open Responses for the original answers and accepted files. Pause intake when you need a break, or archive the form when collection is complete.
Share with the people who need it
A public link.
Or a workspace door.
Gather a customer's feedback without making them join the workspace. Or keep an internal request form available to active workspace members.
Public forms welcome anyone with the link.
Respondents do not need to sign in. Responses are anonymous, even when someone has a workspace session. An email or name question collects supplied contact details.
Private forms require workspace membership.
An active member can respond without access to the destination project or team. Submitting leaves destination access and other responses private.
Keep collection close to your website.
Embed a published public form in an iframe. Choose the HTTPS websites allowed to frame it; the public direct link remains accessible. Private forms open through workspace sign-in.
Keep the supporting detail
The screenshot.
The source.
The actual answer.
Choose permitted file types and an upload limit for each file question. Files are checked and scanned before acceptance, stored privately, and kept with the response and its resulting work or evidence.
Managers can review the original response and its files. Links to work and attachments follow the viewer's current access; public respondents receive a confirmation without internal work or download links.
Signals reports are shared with the workspace. Associations with private projects stay limited to members who can access those projects.
See where requests become workA few useful details
Before the first response.
Which plans include new forms?
Creating, copying, restoring and first publishing a form require Starter or above. Draft, published and paused forms share the workspace's allowance; archiving releases a slot. Work-item and storage limits also apply to incoming responses. Compare current form allowances.
What happens after a downgrade?
Previously published forms can keep collecting, including on Free. Managers can review responses, edit and republish those forms, and pause or resume them. New forms and restorations require current eligibility. Signals forms retain raw evidence while Signals access and paid processing follow the current plan.
Who can manage forms and responses?
Workspace administrators can manage all forms. A project creator can manage that project's forms while they retain access. Team and Signals forms require a workspace administrator. Being able to respond does not grant access to form management or response history.
Can I change the destination later?
The destination is fixed after first publication. Duplicate the form to make a new draft with another destination. The copy has its own capacity slot and starts without the original response history.
How much can a respondent upload?
Each upload question accepts one file. A response can include up to 10 files with a combined maximum of 25 MiB; field and workspace restrictions may be tighter. A failed or unavailable scan blocks acceptance, so the response and resulting work are not partly submitted.
Where can I read the setup details?
The Forms guide covers fields, native mappings, publication, privacy, embedding, response review and plan behavior. Read the Forms guide.
A clearer beginning
Less missing context.
More useful requests.
Give people a simple way to tell you what they need, and give the team the detail to take it from there.
Follow feedback through SignalsCOME TAKE A LOOK
A little less busy.
A lot more together.
Curious? Leave your email. We’ll keep you posted on early access and what’s new.