--- title: "FAQ (DC)" canonical: "https://support.appfire.com/space/SRV/16842836/FAQ%20(DC)" format: markdown --- > Macro (aura-html) ### What is the limit of surveys that I can create? Unlimited. Surveys for Jira has been tested with 10,000+ surveys per project. ### What is the limit of questions in the custom / advanced survey? Unlimited. Some customers use surveys with 50+ questions without issues. ### Can we brand our survey? Yes. You can add your company logo, theme, and colors — Surveys for Jira supports HTML and CSS formatting. ### Can I export survey results? Yes. Data tables support export to CSV, PDF, and XLSX, as well as data copy and table printing. ### Do the surveys support skipping logic? Yes. You can use a JQL filter to control which issues trigger a survey, or use the frequency percentage configuration to control how often the survey is triggered. For example, you can send surveys for issues with "High" priority only. ### I created a survey, but it is not sending. Why? There are a few possible reasons: - The project has not been selected in the app configuration. - The ticket did not reach the status selected as the trigger point. For example, the trigger is set to *Resolved* but the ticket is still at *Waiting for Support*. - The mail frequency is set to less than 100%, so surveys are only sent for a percentage of matching tickets. Set frequency to 100% when testing. ### The survey sent successfully but the email does not display the rating form Some email clients do not render embedded forms correctly. Try a different email client. If the issue persists, use the **Custom Survey** option so that the survey email contains a link to a hosted HTML survey form rather than the embedded form. For background on email form rendering: - [https://www.campaignmonitor.com/blog/post/2435/how-forms-perform-in-html-emai/](https://www.campaignmonitor.com/blog/post/2435/how-forms-perform-in-html-emai/) - [http://www.sitepoint.com/forms-in-email/](http://www.sitepoint.com/forms-in-email/) ### After upgrading to version 3.0, I don't see all survey reports from the previous version The surveys are not deleted. The reduced number of report entries is due to a change in the report data model introduced in version 3.0. The new model was required to support further development. During migration, entries that were missing required data fields could not be moved to the new model and were invalidated. The old data still exists. If needed, it can be accessed by reverting to the previous version of Surveys for Jira. ### Can I send a survey manually, bypassing the trigger conditions? Yes. You can force-send a survey to a specific ticket and recipient without changing the general survey configuration. Use the **Test survey** button for this. ### Is there any follow-up automation I can do based on survey results? Yes. 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 the assignee, or create a follow-up ticket. ### Can I use survey data in an external reporting system? Yes. Use the [REST API](https://appfire.atlassian.net/wiki/spaces/SRV/pages/16843057) to retrieve survey data and work with it in other systems. ### Why do I see "error 500" when I click a survey link from an email? This usually means the required placeholders `#form` and `#SdQuestion` are missing from the Form body field. See [Creating a survey](https://appfire.atlassian.net/wiki/spaces/SRV/pages/16843172) for details. ### Can Surveys for Jira be used to measure NPS? There is no dedicated NPS option, but you can configure a survey with a 0–10 number scale and use the *Rating by issue count* report to calculate the percentage of promoters (9–10) and detractors (0–6), then compute NPS as the difference. This report is available in both the Data Center and Cloud versions. ### Does the Cloud version have the same functionality as Data Center? Core functionality is the same across both deployments, but some features differ due to architectural differences. The table below shows current feature parity: | **Feature** | **Data Center** | **Cloud** | **Note** | | --- | --- | --- | --- | | Permissions to view survey reports, feedback, and ratings | :check_mark: | :check_mark: | | | 1-click survey | :check_mark: | :minus: | | | Survey recipients: single user, user group, multi-user picker, custom | :check_mark: | :check_mark:* | In Cloud: assignee, reporter, custom user, custom group | | Survey email: web link or embedded rating form | :check_mark: | :check_mark: | | | Star rating or yes/no option | :check_mark: | :check_mark: | | | Rating elements: numbers or stars | :check_mark: | :minus: | | | Custom rates count (0–10) | :check_mark: | :minus: | | | Ask users for a comment | :check_mark: | :check_mark: | | | Thank you message | :check_mark: | :check_mark: | | | URL for expired surveys | :check_mark: | :minus: | In Cloud: redirect URL available for answered surveys | | Different question types; required question option | :check_mark: | :check_mark: | | | Preview | :check_mark: | :minus: | | | Test survey | :check_mark: | :minus: | | | Trigger point (status change, JQL match, manual) | :check_mark: | :check_mark: | | | Trigger a SIL script | :check_mark: | :minus: | | | Frequency filter | :check_mark: | :check_mark: | | | Survey branding (email, form, background) | :check_mark: | :check_mark:* | HTML supported in survey email and form | | Custom table report | :check_mark: | :check_mark: | | | Survey dashboard | :check_mark: | :minus: | | | Survey information in the ticket | :check_mark: | :check_mark: | | | Export survey results (CSV, PDF, XLSX) | :check_mark: | :check_mark:* | Cloud: CSV only | | Select color of stars | :minus: | :check_mark: | | | Custom SMTP server | :check_mark: | :check_mark: | | | Jira Service Management support | :check_mark: | :check_mark: | | | Multiple active surveys per project | :minus: | :check_mark: | |