> 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/make-use-of-automation-action.md).

# Make use of automation action

This action generates a public rating link for a selected feedback survey (feedback type) and a specific Jira issue, so you can send customers directly to a ready-to-rate page.

### Jira Automation Action: Get Rating URL (Feedback Survey)

This action generates a **public rating link** for a selected feedback survey (feedback type) and a specific Jira issue, so you can send customers directly to a ready-to-rate page.

#### What you can do with it

* Generate a survey rating URL inside an automation rule using **Generate Public Rating URL** action
* Target the survey to the current issue using `{{issue.id}}` (mandatory for request scoped surveys, optional for project scoped surveys).
  * Note: this is not the issue key, but the issue ID.
* Choose which feedback survey to use by entering its **Feedback Survey ID**.
  * Note: feedback survey ID can be found in the settings page, after selecting the survey tab.
* Use the generated URL inside the `{{createdJiraRatingurl.ratingUrl}}` smart value in downstream automation steps (for example in comments, emails, or custom notifications).
* Preselect a rating in the URL with `defaultRating` query parameter to create one-click rating buttons (1-5 for rating scales, 1-10 for number picker scales).

#### Configuration fields

First of all, insert the Generate Public Rating URL action into your automation rule. On the configuration dialog, you will see the following fields:

* `Issue ID` (required)
  * Accepts Jira issue ID (not issue key).
  * You can use smart values like `{{issue.id}}`.
  * Example: `12345` or `{{issue.id}}`.
* `Feedback Survey ID` (required)
  * Enter the numeric ID of the feedback survey from the app Settings page.
  * Copy and paste the ID from the settings page.
  * Example: `12345`.

#### Validation and behavior

* If the Feedback Survey ID matches an existing survey, the form confirms which survey will be used.
* If the survey ID cannot be found, you can still save, but the rule may fail at runtime.
  * For example, you may bypass this validation when using a smart value for the Feedback Survey ID.
* During rule validation, inputs are locked to avoid accidental changes.

#### Advanced usage: prefilled rating links

You can append `defaultRating` to the generated URL:

* For 5-star/rating scales: `defaultRating=1..5`
* For 10-point number scales: `defaultRating=1..10`

Example use case: build email buttons like “Rate 5/5” that open the survey with a preselected score.

#### Our recommended way to use it

Send rating survey links via the Email This Issue automation action ([by following this guide](https://docs.meta-inf.hu/email-this-issue/outgoing-emails/automation-action/myra-integration)) or the native Jira e-mail action, and get feedback on multiple aspects, like Net Promoter Score (NPS), Customer Satisfaction Score (CSAT), or Customer Effort Score (CES), without the need to manually send out links.

#### Common pitfalls

* Use **issue ID**, not issue key (`PROJ-123` is not valid here).
* Make sure the Feedback Survey ID is copied exactly from Settings.
* If you use smart values, verify they resolve in your rule context.


---

# 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/make-use-of-automation-action.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.