> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/create-new-feedback-survey.md).

# Create new Feedback Survey

To build a custom feedback survey, navigate to the Settings tab and click the **+ New** button.

### Start from a template (optional)

Before filling in the form, you can pick a pre-filled template from the template selector at the top of the page — it pre-fills the fields below, which you can still adjust before creating the survey. Skip this (or choose the custom option) to start from a blank form.

As you fill in the form, a **live preview** on the right shows exactly how the survey will look to customers.

### Fields

Please provide the following details:

* **Survey name**: A unique internal identifier for your survey.
  * *Reserved names:* the names csat and nps are reserved for Myra's built-in surveys and cannot be used. These built-in surveys are visible at the space level:
    * csat: Operates at the request scope.
    * nps: Operates at the space scope.
  * Unlike Collection scope and Response format below, the survey name **can be changed later**, from the **Survey builder** tab.
* **Collection scope:** The context in which the survey operates (Request, Project, or Public). See [Understand Survey scopes](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/understand-survey-scopes.md).

<div align="center" data-full-width="true"><figure><img src="https://3520262872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkIFt9YZMR8h3a9n0Km6u%2Fuploads%2Feu1wbn3H391Oeb0rJHZW%2Fscopes.png?alt=media&#x26;token=d25cdd9a-e125-41d2-8aee-f71d7bc63804" alt="" width="375"><figcaption><p>Scopes</p></figcaption></figure></div>

* **Score calculation strategy:** The mathematical method used to generate this question's score (Average, Sum, NPS, etc.). See [Understand Calculation strategies](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/understand-calculation-strategies.md).
  * NPS requires **Number Pick** as the response format below.
  * Unlike Collection scope and Response format, this **can be changed later** — from this question's editor in **Survey builder** (locked to Average for the built-in CSAT survey).

<figure><img src="https://3520262872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkIFt9YZMR8h3a9n0Km6u%2Fuploads%2FTt4ilWAM6BxH31p86ayG%2Fcalculation_strategies.png?alt=media&#x26;token=47a4340b-18fd-4ab0-b420-f551b0ae24aa" alt="" width="375"><figcaption><p>Calculation strategies</p></figcaption></figure>

* **Response format:** The input method customers will use for the main question (Rating, Number Pick, or None). See [Understand Field type](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/understand-field-type.md).

<figure><img src="https://3520262872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkIFt9YZMR8h3a9n0Km6u%2Fuploads%2FymttUEaIM7FieeN4oOr7%2Ftypes.png?alt=media&#x26;token=30bb6ea2-f55e-4377-84f6-20c216c7ce1f" alt="" width="375"><figcaption><p>Field types</p></figcaption></figure>

* **Question shown on forms:** The prompt customers see above the main input (e.g. "How did we do today?").
* **Displayed text on widgets:** The human-readable name shown to users in the survey widget, page, and reports.
* **Measurement range (days):** Shown only when the survey has a real calculation strategy — the time window used to calculate the displayed score.
* **Enable comments:** Shown unless Response format is None. Adds a comment question under the main one; you can turn it off later, per question, in **Survey builder**.
  * When on, you also set the **comment question text** and **comment placeholder text** shown to customers.
* **Email question text:** Every survey — regardless of scope — includes an optional email question, so customers can leave a way to reach them back. Set the prompt text shown above that field here.

{% hint style="warning" %}
Only **Collection scope** and **Response format** are permanent. Once the survey is created, these two settings *cannot be changed later* — choose them carefully. Everything else, including the survey name, calculation strategy, question text, and comment settings, can be adjusted afterward.
{% endhint %}

### After creation: Survey Builder

Creating the survey only sets up its main question, plus the automatic comment and email questions. To add more questions, reorder them, hide ones you don't need, or fine-tune any of the settings above later, use the **Survey builder** tab — see [Survey Builder](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/survey-builder.md).

#### Where to Create Your Survey

Global vs. Space Surveys: What's the difference?

* **Global App**: Surveys created here are always assigned the Public scope and must be manually linked to a project. They are designed for external collection, giving you a standalone URL and embed code so customers can leave feedback without logging into Jira.
* **Space App**: Surveys created directly within a project are automatically linked to that specific project. By default, they are designed for internal Jira workflows and will not collect feedback externally, unless you set their scope to Public.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/create-new-feedback-survey.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
