Forms are the best way to collect structured information in Jira Service Management: a hardware request asks for the department, cost center and laptop model; an onboarding form asks for the start date and the equipment needed. Then someone asks "how many laptop requests came from Finance this quarter?" and you find out that form answers are not searchable with JQL. Filters, queues, dashboards and automation conditions cannot see them.
There are several ways to work around this with what Jira Cloud already gives you. Here they are, with the trade-offs of each.
1. Link the important questions to Jira fields
In the form builder, a question can be linked to a Jira field. The answer is then copied into that field when the form is submitted, and the field is searchable like any other: Department = Finance.
This is the best option when:
- you know in advance which few questions people will want to search on,
- a matching field already exists, or you are happy to create one.
The limits:
- every question you want to search needs its own field, and a site with dozens of forms soon has hundreds of custom fields,
- it only works for new submissions - answers given before you linked the question stay in the form only.
2. Copy answers with automation
When linking is not an option, an automation rule can copy an answer into a field, a label or a comment.
- Trigger: Forms submitted.
- In the form builder, give the question a field key (side panel). Keys are case-sensitive.
- Use the answer as
{{forms.last.department}}. For choice questions, add .label: {{forms.last.department.label}}. - Action: Edit work item (set a field) or Add label.
Labels are handy for one or two values you filter on often (dept-finance). Like linking, this only applies to forms submitted after the rule exists. Note that saving a form without submitting it fires nothing, so answers on open (unsubmitted) forms are never copied.
3. Export the answers to a spreadsheet
For a one-off report, the built-in XLSX exports are the fastest route:
- One request: open the form on the work item, then the ... menu - Download XLSX.
- Every response to one form: Project settings - Request management - Forms, then ... next to the form - export. Project admins only.
- A filtered list with Jira fields: run a JQL search, add the Jira columns you want, then Export - Export XLSX (form data). You get the Jira fields plus the form answers for issues that have the selected form.
One known issue: when the search returns more than 50 rows, the issue keys appear only every 50 rows in the file (JSDCLOUD-11912). The workaround is to export 50 issues at a time and combine the files.
From there, a pivot table answers "how many per department" in a minute. The catch is that it is a snapshot: nothing updates when the answers change, and nobody else sees it unless you share the file.
4. Design forms that are easy to report on
Whichever route you take, a few habits in the form builder save work later:
- Prefer dropdowns, radio buttons and checkboxes over short text for anything you will count. "Finance", "finance" and "Finance dept" are three answers to a spreadsheet.
- Set a field key on every question you might use in automation. The default keys are ids that nobody remembers.
- Keep the same wording for the same question across forms ("Department" everywhere, not "Team" on one form), so answers line up in an export.
- Use conditional sections for different request kinds rather than one long form, so unanswered questions do not drown the answered ones.
5. What about Rovo?
Rovo answers from the work item's fields, description and comments, but it does not read form answers today (ROVO-317). If you want Rovo or other AI tools to see form data, it has to be copied somewhere they can read it - a linked field from step 1 or a comment from step 2.
A faster way, if you have many forms
Disclosure: I'm the developer of Formsight at AIGA Tech, a Marketplace app built for exactly this.
The steps above work well for a few important questions. When people want to search any answer on any form, including old submissions and forms that are still open, I built Formsight. It runs on Atlassian's own platform and:
- makes every form answer searchable with JQL, with no field per question:
formAnswer = "Department: Finance", formText ~ "macbook", formsOpen > 0, so filters, queues, dashboards and automation conditions can use them, - indexes existing requests too, and keeps up with forms that are saved without being submitted,
- gives a search page and an answer report per form, with charts and CSV export,
- lets Rovo read form answers, through its own agent and in plain Rovo chat.
Search and reports run with the viewer's own Jira permissions, so nobody sees answers on requests they cannot open.
Formsight on the Atlassian Marketplace
Happy to answer questions about any of the steps above, with or without the app. How do you report on your form answers today - linked fields, automation, or exports?
