Project Setup
Form Fields
Configure what reporters see and fill in.
The Form Fields tab controls the feedback form reporters see after annotating a screenshot.
Available fields
| Field | Type | Notes |
|---|---|---|
| Title | Text / textarea | Optional separate title line (depends on setup) |
| Description | Textarea | Where the reporter describes the problem |
| Name | Text | Reporter's name |
| Reporter's email | ||
| Assignee | Select | Populated from your tracker's synced team members |
| Priority | Select | Populated from your tracker's priority levels |
| Label | Select | Populated from your tracker's labels (when the tracker uses labels) |
For each field you can:
- Show or hide it
- Reorder it
- Set a custom placeholder
- Mark it required
Options come from your integration
Assignee, priority, and label options aren't typed manually — they're fetched from whichever tracker you connected on the Integration tab. Toggle each option's visibility (via the eye icon) from the Project's Overview page.
Azure DevOps fields
When the Project is connected to Azure DevOps, the form can also include:
| Field | Notes |
|---|---|
| Severity | Shown instead of a generic “Priority” label when the process supports it on Bugs |
| Parent | Typeahead to link the new work item under a User Story, Product Backlog Item, etc. |
| Area | Classification path (overrides the integration default when set) |
| Sprint | Iteration path (overrides the integration default when set) |
| Tags | Azure tags (search / create) |
Which of these appear depends on the connected project’s process and synced metadata.
Should reporters pick a priority or assignee themselves?
It depends on your workflow:
- Public-facing widget — hide assignee/priority; let your triage rules or a default assignee handle routing instead.
- Internal QA team — showing priority and assignee gives testers direct control, at the cost of one extra decision per report.
Screenshot
