This day has come! We are happy to announce v4.0 of Surveys for Jira – the most configurable and powerful survey app on the market – and it is stronger than ever.
This page describes how you can create a survey for the versions 4.0 and above. The concepts and logic are similar to the previous versions but for your convenience we have kept documentation for the previous versions here.
- Ensure that your user has Admin permissions in the Jira project where you want to create a survey
- Ensure that you have Surveys for Jira installed and configured
- Ensure that you have the necessary project(s) selected for the surveys
Creating a survey
The quickest you can create a survey is with just one click so you can start on your survey journey in less than a minute. Click Create 1 Click Survey and that's it. It's created using the most standard settings like a 5 star rating scale and all other fields pre-filled already. Just activate it in the survey table and you are ready to go!
But you are probably here for configurability and freedom. Here's how you create a survey with all that:
- In the Jira project where you want to create a survey, go to the project settings.
- In the SURVEYS FOR JIRA section on the left panel, click Surveys, which will open the Project Surveys page.
- Click Add New Survey.
- Go through the survey wizard and fill out the necessary fields as shown in the sections below.
- Click Save.
The Email tab is used for specifying details on how a survey email will look like and which content it will have.
Deprecated in v4.0.0.
In the new versions of Surveys for Jira you can edit the name for your surveys right in the surveys table, no need to go to the settings of each individual survey. Just click the name of the survey in the table and enter a new one. This will help you differentiate between your surveys. For instance, "Christmas branded survey", "Default survey", "Test survey on September 15" will instantly help you find the necessary one.
|Email Subject||Enter an email subject that you want your end users to see in the survey email.|
In most cases survey recipient would be the reporter of the ticket.
In addition to that, our users also found it to be convenient to be able to select a different user or even send surveys to several recipients.
You can send surveys to:
- Single User – that can be a ticket Assignee, Reporter, or a custom single user that exists in your Jira.
- User Group - enables you to send a survey to the selected Jira user groups. Be aware that group survey is sent once per ticket. This option is useful if you want to survey a set group of Jira users, survey your project team in the end of the sprint (sprint retro), survey your QA team separately, or HR department in your company for instance.
- Multi User Picker CF – this option is extremely popular with companies that want to survey multiple people but sets of those people are dynamic and can be different for every ticket, so a multi user picker custom field is used for that.
For example, upon resolving a bug you can survey all ticket participants, not just a ticket reporter, and survey participants might differ for any particular ticket. Like the previous option, note that the group survey will only be sent once per ticket.
- Custom - with this option you can create any custom surveys for any specified Jira users, you are not limited by a user group. Select multiple Jira users by entering their names or emails. Like the previous option, note that the group survey will only be sent once per ticket.
For this option you can select both internal Jira users and customers of your Service Desk support portal, that is your clients that created accounts in your support portal.
|Use project email for 'Reply To'||By default, the surveys are sent from Jira service account, and people cannot reply to the survey emails. You can opt to select the email from the project settings as a reply-to email for the surveys. |
Here you can design a body of your survey that the end user will receive. You can use the placeholder variables in order to personalize your email template. To add a placeholder variable just click it in a list of placeholders.
The placeholder values wrapped by "$$" signs will be populated by the information submitted in the ticket that triggers the survey. The following placeholder variables are available:
This is how placeholders might be used in the survey settings:
This is how the placeholders will look in the actual email sent to the user. They are replaced with actual values from Jira (highlighted). Note how the $$weblink$$ placeholder shows as a link to the survey.
Click this button to get a sense how your survey email might look like for a survey recipient.
This will not trigger any surveys but will just show a preview of a survey email as it's configured in the settings.
|Survey Email Include|
You can customize your survey emails to include either a survey rating scale or to display a link to your survey form that you can also further customize.
You can change the text for the link or show it as an image instead. For example, you can display the link to the survey as a button in your survey email. Use Upload resources to add a custom image, then edit the weblink and use the Insert resources button to use your visual assets.
|Work With||Depending on how you want to shape your surveys you can choose to work with star rating or specify a yes/no question as the main survey question for the users.|
Some companies find it useful to work with a number scale as an alternative to a star scale. This is just a matter of preference but we made sure that you can use both a star system (like Amazon or Google) or a number system (like Booking).
For the number scale we have also implemented an option to include a zero rating as some companies find it useful in their surveying processes.
You can choose to have a default 5 rating scale or decide to simplify it to less rating elements (3 - Good, 2 - Medium, 1 - Bad for instance) or have more granularity and change the rates count up till 10 for more sophisticated surveys.
Your users are notified about the surveys via email and then can open a survey form by clicking a rating scale or a link embedded in the email. Use the Form tab to configure your surveys once the users open a survey form from the email. This is the essence of the survey where you put all your survey questions.
|Here you specify the introductory text for your survey form and define general survey form settings.|
Enter an introductory text for your survey. Use a WYSIWYG editor to build your own template.
You can use CSS to give a branded look to your surveys - pumpkin rates for the Halloween time surveys, smileys for April 1, company logo or corporate background are just among the few ideas of what's possible. Click the </> button to upload your coded template.
If you want to upload and reference images, use the Upload Resources and Insert Resources buttons.
|Ask user for a comment||If you would like your users to submit a comment along with their star rating, select "Yes" for this option. You can set up your surveys to ask for the comment only if a negative rating is given.|
|Thank you message|
Appreciate feedback your users provide with this message. It's shown to the user after they submit survey answers. Alternatively, you can select not to notify a user.
|URL for expired surveys|
If for some reason, a user opens the survey which has already expired, they can be redirected to your Service Desk portal or any other URL that you specify in this field.
For you to have accurate data there is no possibility to answer the survey again if it was answered already. If a person submits their feedback, goes to the email and tries to enter a survey again, they will be presented with a message and a link where they can submit more feedback or raise another ticket. Usually companies like to enter a URL for their Service Desk portal so that there is still connection with the users.
|Here you can add various types of questions to your survey, define their order, and define other question related settings. |
Click Add Question to start adding custom questions to your survey. Once you do, the question dialog opens where you can specify the question text, whether a question is required to answer, add answer options for the single and multiple choice questions.
Starting with 4.0.3 version you can select Star Rating as an option for your Questions ranking.
As you add questions to your survey they are displayed in the Questions table.
In the table you can perform the following actions with the survey questions:
- Modify the question text. This is an easy inline edit but we recommend that you double check the answer options in the question dialog to make sure they connect well with a new question text.
- View the type of the question
- Change whether a question is required or not
- Change the order of the questions in your survey
- Deactivate questions. This is a feature that our users love because it allows them to temporarily not survey their audience on certain questions but still have those questions stored in case they are needed again.
- Edit and delete questions
Once you specify the form settings and add the necessary questions to your survey, it's time to save your changes. Once you do that, click the Preview button. It opens a dialog where you can see how your survey will look like for your users. This will not trigger any surveys and is a convenient way to do a quick health check without emailing anyone.
If you actually want to send a test survey, we recommend that you use the Test survey button described here.
On the Conditions tab you define how your surveys should be sent, whether they should be filtered, and what actions should be done based on survey activity.
|'Trigger Point' section|
|Use this section to define whether to send survey for all tickets meeting trigger point conditions or only certain ones.|
Select the status that will trigger a survey. You can set different issue types separately. For instance, you can opt to only send surveys for the "Bug" issue type.
You can create a custom JQL query to serve as a trigger point for the survey. Then you can just select your saved filter for this option. For example, you can survey on the tickets that belong to a certain product component or filter out requests of a certain type only.
|Send survey once per issue|
Sometimes it happens that a ticket is resolved, a recipient replies to the survey and then for some reason the ticket is reopened, someone works on it and resolves a ticket again. This might trigger a survey to be sent to a recipient again, and sometimes this is exactly what the companies want (survey on how the service was provided this time) but sometimes companies wish not to overwhelm and exhaust their recipients with too many surveys. You can opt to only send a survey once per issue.
If a recipient answers a survey for the same ticket again, then the latest rating is shown in the ticket but you can see the history of the previous replies in the Survey Feedback tab and in the app reports.
|Check every issue change||Usually the survey triggers are checked when the ticket status changes but if you want you can run this check on every issue change. We recommend that you leave this checkbox clear unless you have a strong need for it.|
Trigger a SIL script when survey is sent
Trigger a SIL script when survey feedback received
If you also use our other app Power Scripts, you can add automation to your surveys as well.
Starting with v3.2.3 for Jira 7 and v3.3.3 for Jira 8, we have added the possibility for you to trigger other actions once the survey is sent or survey feedback is received.
For instance, you can have an automatic comment posted in the ticket indicating that the survey was sent (as on the picture below) or change assignee, create another ticket, and so on. Now the endless possibilities of SIL are brought into Surveys for Jira.
|You can further filter the surveys sent based on the values in the certain fields. For example, you can ask for feedback for every major bug but for the minor ones - send surveys for only 10% of those.|
|Send surveys for all tickets||If you select this option, then surveys will be sent for all tickets in this project that meet the trigger conditions.|
|Filter surveys by|
You can filter your surveys even further.
By default, the app draws on the Priority field but you can select another single select custom field.
For example, you can:
- Survey people for all critical and major bugs (100%), send the survey to only 50% of the medium bugs randomly, and not survey people on minor and trivial bugs at all (0%).
- Survey people that report bugs on Windows (100% for the Operating System custom field) and not survey the ones that are on Mac OS X or other operating systems (0% for other values for this custom field) so that people using other operating systems are not affected by this.
Testing your surveys
You can send an actual survey to test the complete flow before you turn the survey functionality on for all your users. Once you click this button, a dialog form appears where you specify the following information:
- Send survey for – select a ticket for which you want to send a test survey. We recommend that you create a separate test ticket for that in order not to mix with your actual survey data.
- Test Recipient – even though you might have a different recipient in your survey settings, it's convenient to be able to just set your email manually so as not to spam the actual survey recipients and not to change any survey settings during testing.
That's it. Click Send, and the app will send a survey with all specified settings that you configured. That is you will be able to see how the email is shaped with the actual values instead of placeholders, how survey form looks like with all questions configured and whether the branded UI looks like you wanted to.
You can answer the survey and then check how the rating and answers are displayed in the ticket, what data you receive in the reports.
Not that this button is only clickable when all conditions for sending an actual survey are met, that is all required fields are filled in and the Email body field contains the $$weblink$$ placeholder variable. This is to ensure that the app will be able to actually send a test survey.
Analyzing survey results