---
title: "Create a survey (DC)"
canonical: "https://support.appfire.com/space/SRV/16843172/Create%20a%20survey%20(DC)"
format: markdown
---
> Macro (aura-html)
This page describes how to create a survey in Surveys for Jira DC version 4.0 and above.
## Prerequisites
- Your user has Admin permissions in the Jira project where you want to create a survey
- Surveys for Jira is installed and configured
- The project is selected in the app configuration
## Creating a survey
The quickest way to create a survey is with one click: click **Create 1 Click Survey** to create a survey using standard settings (5-star rating scale, all fields pre-filled). Activate it in the survey table and you're ready to go.
To create a fully configured survey:
1. In the Jira project, go to the project settings.
2. In the **Surveys for Jira** section on the left panel, click **Surveys** to open the **Project Surveys** page.
3. Click **Add New Survey**.
4. Go through the survey wizard and fill out the necessary fields.
5. Click **Save**.
> ⚠️ - After configuring survey settings, activate the survey in the project's survey list.
> ⚠️ - Only one survey can be active per Jira project. Activating a new survey deactivates any currently active one.
## Survey tabs
### Email
The **Email** tab specifies how the survey email will look and what it will contain.
| **Field** | **Description** |
| --- | --- |
| **Survey Title** | Deprecated in v4.0.0. Survey names can now be edited directly in the surveys table. |
| **Email Subject** | Enter the email subject recipients will see in the survey email. |
| **Survey Recipient** | In most cases, the survey recipient is the ticket reporter. You can also send surveys to multiple recipients:
> ℹ️ Group survey is available from v4.0.0.
- **Single User** — Assignee, Reporter, or a custom user from Jira.
- **User Group** — Sends to all members of a selected Jira user group. Sent once per ticket.
> Macro (inline-media-image)
- **Multi User Picker CF** — Sends to users in a multi-user picker custom field. Useful when recipients differ per ticket. Sent once per ticket.
> Macro (inline-media-image)
- **Custom** — Select any Jira users by name or email, including Service Management portal customers. Sent once per ticket.
> Macro (inline-media-image) |
| **Use project email for 'Reply To'** | By default, survey emails are sent from the Jira service account and recipients cannot reply. Enable this option to use the project email as the reply-to address. |
| **Email Body** | Design the survey email body. Use placeholder variables to personalize the template — click a placeholder in the list to insert it. Values wrapped in `$$` signs are populated from the ticket that triggers the survey.
> Macro (nested-table)
> ⚠️ You must include the **$$weblink$$** placeholder — it generates the URL to your survey. Use the **Edit** button to customize the link label or replace it with an image. |
| **Survey Email Include** | Choose to embed a rating scale in the email or send a link to the survey form. You can display the link as text, a button, or a custom image. Use **Upload resources** to add images, then **Insert resources** to reference them.
 |
| **Work With** | Choose between a star rating scale or a yes/no question as the main survey question. |
| **Rating Elements** | Select between a star scale or a number scale. For the number scale, you can also enable a zero rating option. |
| **Rates Count** | Set the number of rating elements — from 1 to 10. The default is 5.
> ⚠️ Reset survey statistics before changing the rating scale to avoid misleading data in reports. For example, a 5-star response from a previous scale would appear differently on a 10-star scale. |
### Form
Use the **Form** tab to configure what recipients see when they open the survey form from the email.
| **Field** | **Description** |
| --- | --- |
| **Form section** |
| Specifies the introductory text and general settings for the survey form. |
| **Form body** | Enter introductory text for the survey form using the WYSIWYG editor. You can use CSS (click **** to open source) to brand the form. Use **Upload Resources** and **Insert Resources** to reference custom images.
> ⚠️ You must include **#form** and **#SdQuestion** at the end of the form body. These render the rating form and questions.
 |
| **Ask user for a comment** | Enable to ask recipients for a written comment along with their rating. You can configure this to appear only when a negative rating is given. |
| **Thank you message** | Shown to the recipient after they submit their answers. Alternatively, disable to show no message. |
| **URL for expired surveys** | If a recipient opens a survey that has expired or was already answered, they are redirected to this URL. Typically used to point to the Service Management portal. |
| **Questions section** |
| Add, order, and configure custom questions for your survey. |
| **Question dialog** | Click **Add Question** to add a custom question. Specify question text, whether it's required, and answer options for single/multiple choice questions. From v4.0.3, **Star Rating** is also available as a question type.
 |
| **Questions table** | Added questions appear in the Questions table where you can:
- Edit question text inline
- View question type
- Toggle required/optional
- Reorder questions
- Deactivate questions temporarily without deleting them
- Edit or delete questions |
| **Preview** | Click **Preview** to see how the survey form will appear to recipients. This does not trigger any survey sends.
 |
### Conditions
The **Conditions** tab defines how surveys are sent, how they are filtered, and what actions occur based on survey activity.
| **Field** | **Description** |
| --- | --- |
| **Trigger Point section** |
| Define whether to send surveys for all tickets meeting the trigger conditions or only specific ones. |
| **Status change** | Select the status transition that triggers a survey. You can configure different issue types separately.
 |
| **JQL match** | Use a saved JQL filter as the trigger condition. For example, trigger only on tickets matching a specific component or issue type.
> ⚠️ The filter must be [shared](https://confluence.atlassian.com/adminjiraserver0900/managing-filters-1142255888.html) with users, groups, or projects that have access to the tickets. |
| **Send survey once per issue** | Enable to prevent sending the same survey to a recipient more than once for a given ticket, even if the ticket is reopened and resolved again.
> ⚠️ Group surveys are always sent once per ticket. The latest rating displays on the ticket; all historical responses appear in the Survey Feedback tab and reports. |
| **Check every issue change** | By default, trigger conditions are evaluated on status changes only. Enable this to check on every issue change. Leave this disabled unless specifically required. |
| **Trigger a SIL script when survey is sent**
**Trigger a SIL script when survey feedback received** | If you also use [Power Scripts](https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation), you can trigger SIL scripts when a survey is sent or when feedback is received — for example, to add a comment, change assignee, or create a follow-up ticket.
 |
| **Frequency section** |
| Further filter which tickets trigger a survey — for example, survey 100% of critical bugs and 10% of minor ones. |
| **Send surveys for all tickets** | Sends a survey for every ticket that meets the trigger conditions. |
| **Filter surveys by** | Filter by a single-select field (default: Priority) and assign a percentage for each field value. For example, send surveys for 100% of high-priority issues and 0% of low-priority ones.
> ℹ️ The field must be a single-select type with [global context](https://confluence.atlassian.com/adminjiraserver/configuring-custom-field-contexts-1047552717.html). Project-specific custom field options cannot be fetched. |
## Testing your surveys
Click **Test survey** to send an actual survey email to a specified recipient and ticket. Specify:
- **Send survey for** — the ticket for which to send the test survey
- **Test Recipient** — the email address to send the test to, regardless of the configured survey recipient
> ℹ️ For testing, ensure [Disable empty JQL queries](https://confluence.atlassian.com/adminjiraserver/configuring-jira-application-options-938847824.html#ConfiguringJiraapplicationoptions-optionsOptions) is disabled in Jira System settings.
## See also
- [Analyzing survey results](https://appfire.atlassian.net/wiki/spaces/SRV/pages/16843152)