> 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/understand-collection-rules.md).

# Understand Collection rules

Collection Rules let you control when a survey is shown and who can submit it. They are **restriction rules**: add them only when you want to limit collection.

Each Feedback Survey has its own independent rule set. These rules affect request panels, portal collection, standalone links, and embedded survey collection wherever that survey can appear.

#### How rules behave <a href="#how-rules-behave" id="how-rules-behave"></a>

* **Enable Collection** must be turned on before any rule can matter.
* With **no rules**, collection is allowed.
* If **all rules are disabled**, collection is also allowed.
* If one or more rules are enabled, **all enabled rules must pass** for the survey to appear.
* Some rules only apply to certain survey scopes.

{% hint style="info" %}
Legacy **Always Allow** and older **Cooldown** configurations are no longer used as addable rules. Existing older setups are migrated automatically to the current rule model.
{% endhint %}

#### Available Rule Types <a href="#available-rule-types" id="available-rule-types"></a>

Currently, Myra offers the following Collection Rules:

* **Date Range** (*Only during a date range*)
  * Show the survey only between the selected start date and end date.
* **Day of Week** (*Only on selected days*)
  * Show the survey only on selected days of the week.
* **Last Submission** (*Minimum time since last submission*)
  * Show the survey only if enough time has passed since the same user last submitted this survey.
* **Last Resolved** (*Minimum time since last resolved issue*)
  * Show the survey only if enough time has passed since the reporter's most recently resolved Jira issue. This uses Jira's issue resolution date — it is **not** limited to the current request.
* **Time since request resolved**
  * Show the survey only after the configured amount of time has passed since **this request** was resolved (its resolution date is filled in). Request-scoped surveys only.
* **Request Closed** (*Only after request is closed*)
  * Show the survey only after the Jira Service Management request is closed.
* **Reporter Only** (*Only the reporter can submit*)
  * Show the survey only to the reporter. Other users cannot submit feedback.

{% hint style="info" %}
**Last resolved** vs **Time since request resolved**

* **Last resolved** looks at the reporter's *most recently resolved issue anywhere* — useful to avoid asking for feedback too soon after another ticket closed.
* **Time since request resolved** looks only at *this* request's resolution date — useful to wait a cooling-off period on the same ticket before showing the survey.
  {% endhint %}

#### Configuring Your Rules <a href="#configuring-your-rules" id="configuring-your-rules"></a>

To manage your collection strategy, open the survey and go to the **Collection** tab.

1. **Enable Collection:** Turn Feedback Collection on within the Collection tab before any rules can take effect.

![Enable collection](https://cdn.sandbox.getmyra.app/docs/collection/collection-tab.glossy.png)

{% stepper %}
{% step %}

### Add a Rule

Click **Add Rule** and select the rule type you want to use. The picker only lists types that apply to this survey's scope.

![Add a collection rule](https://cdn.sandbox.getmyra.app/docs/collection/add-rule-form.glossy.png)

![Select rule type](https://cdn.sandbox.getmyra.app/docs/collection/rule-types.glossy.png)
{% endstep %}

{% step %}

### Name and Describe

Assign a unique name to your rule. (*Rule names cannot be changed once saved.*) Add a short description if you want to document the rule's purpose for your team.
{% endstep %}

{% step %}

### Toggle Status, Configure, Delete

Once created, each rule can be switched on or off independently. This lets you pause a restriction without deleting it.

![Delete, configure, and toggle rule status](https://cdn.sandbox.getmyra.app/docs/collection/rule-card-actions.glossy.png)
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Default CSAT collection rules cannot be deleted.
{% endhint %}

**Default behavior:** Most newly created surveys start with no collection rules. Built-in survey defaults are described on the Built in Feedback Surveys page.

#### Rule & Scope Compatibility Matrix <a href="#rule-and-scope-compatibility-matrix" id="rule-and-scope-compatibility-matrix"></a>

Because Myra Feedback Surveys can operate under different scopes, not all rules are applicable in every context.

|                                 | Request scope | Project scope | Public scope | Notes                                                                 |
| ------------------------------- | ------------- | ------------- | ------------ | --------------------------------------------------------------------- |
| **Date range**                  | 🟢            | 🟢            | 🟢           | Available for all scopes.                                             |
| **Day of week**                 | 🟢            | 🟢            | 🟢           | Available for all scopes.                                             |
| **Last submission**             | 🟢            | 🟢            | 🟢           | Not offered for the built-in CSAT survey.                             |
| **Last resolved**               | 🟢            | 🟢            | 🔴           | Uses the reporter's most recently resolved Jira issue.                |
| **Time since request resolved** | 🟢            | 🔴            | 🔴           | Uses **this** request's resolution date. Request-scoped surveys only. |
| **Request closed**              | 🟢            | 🔴            | 🔴           | Request-scoped surveys only.                                          |
| **Reporter only**               | 🟢            | 🔴            | 🔴           | Request-scoped surveys only.                                          |


---

# 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/understand-collection-rules.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.
