> 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/users-guide/release-notes.md).

# Release notes

## Release notes

### October 2026

#### Survey logo and background

The **Appearance** tab now lets you upload branding images stored securely for your site:

* **Survey logo** — shown in the corner of the survey form (standalone pages, website embeds, Help Center). PNG, JPEG, WebP, or SVG · max 512 KB.
* **Survey background** — full-page backdrop on the **standalone** public survey page only. PNG, JPEG, WebP, or SVG · max 2 MB.

See Appearance.

#### Testimonials

Mark feedback items as anonymous testimonials and show them in a carousel on the Customer Portal and on your website. Every survey form also shows a privacy notice above Submit.

See Testimonials.

#### Automation webhooks

Connect a survey to a Jira Automation **Incoming webhook** so every submission can create issues or run other rule actions. Myra sends the payload; your rule decides what counts as negative.

See Automation configuration.

#### Built-in German and Spanish

Translation Studio ships with built-in **German** and **Spanish** label packs you can activate or customize.

See Translation Studio.

### September 2026

#### Survey Builder

Every survey is now a list of questions you can edit from the **Survey builder** tab:

* The main question, comment question, and email question are created automatically.
* Add extra **Rating**, **Number Pick**, **Text**, or **Embed field** questions.
* Reorder, hide, or delete questions. Hidden questions stay reportable; deleted questions drop out of future reports.
* The built-in CSAT survey uses the same screen, but extra questions cannot be added because answers are stored on the Jira request.

See Survey Builder.

#### Appearance

A new **Appearance** tab brands customer-facing forms and widgets:

* **Theme color** — recommended palettes or a custom accent. Score widgets keep a neutral background.
* **Roundness** — None, Rounded, Pill, or a custom 0–24 px radius.
* **Rating symbols** — Stars, Faces, Hearts, or Hands for 1–5 rating questions.

Logo and page background uploads landed in October 2026 — see that section above, and Appearance.

#### Embed fields

Website collection embeds can attach hidden context (for example a tenant id) with `data-myra-fields`. Respondents never see these values; admins see them in reports and CSV export.

See Embed fields.

#### Inline website embeds

Besides the popup button (`data-myra-survey`), **Sharing & embed** now also provides an **Inline form** snippet (`data-myra-survey-inline`) that renders the survey directly on the page.

See Collect Feedback on Your Website with Myra.

#### Per-question widgets

Each Rating or Number Pick question with a calculation strategy can show its own score widget on the portal, Help Center, or an external website. Captions are set per question as **Widget display text**.

See Display configuration.

#### Reports

Survey reports now include:

* Per-question scores, charts, and table columns for extra Rating/Number Pick questions.
* A **Submission details** modal when you click a row.
* A column picker (remembered per survey), sorting, and **Export CSV**.
* **Ask Rovo** — when Rovo is enabled, opens the **Myra Feedback Analyst** agent on the current survey and date range.

See Myra Reports.

#### Time since request resolved

Request-scoped surveys can use a new collection rule: **Time since request resolved**. The survey is shown only after the configured time has passed since **this** request's resolution date. This is different from **Minimum time since last resolved issue**, which looks at the reporter's most recently resolved issue anywhere.

See Understand Collection rules.

#### Other improvements

* Marketplace review prompt on reports after enough submissions.
* Neutral score-widget backgrounds so theme color does not wash out the score.
* Collection-rule labels and restrictive-only behavior (legacy Always Allow / Cooldown are no longer addable).
* Authorization hardening for survey settings, rating URLs, and report queries.

### July 2026

#### Website embed API (breaking change)

Myra's external website embedding has been redesigned:

* **One script per website** — install `widget-embed.js` once in your page `<head>`.
* **Collection embeds** use `data-myra-survey` markup on buttons or links; clicking opens a popup form.
* **Score display embeds** use `data-myra-widget` div markup.
* The previous per-survey `window.myra_widget_<id>.open()` API has been removed.

See Collect Feedback on Your Website with Myra for the updated setup guide.

#### Translation Studio

Manage multi-language survey copy from the new **Translations** tab in survey settings:

* Create language packs with BCP-47 tags (e.g. `de`, `fr-FR`).
* Override form labels, button text, and status messages per language.
* Preview changes live before saving.
* Activate a language pack to show it on portals, public survey pages, and embed widgets.

See Translation Studio for details.

#### Guided tours

Myra now includes in-app spotlight tours to help admins get started:

* **First survey tour** — walks through creating a survey, enabling collection, and copying a public link.
* **Report insights tour** — explains scores, feedback items, and creating linked issues.
* **Translation Studio tour** — introduces language packs, label editing, and activation.

Tours can be dismissed at any time and do not block normal app usage.

See Guided tours for the full list.

#### Portal survey carousel

When multiple **Project**-scoped surveys are collectible on the JSM portal at the same time, customers now see them in a multi-step carousel with progress indicators, Back/Next/Skip navigation, and a Finish action — instead of stacked forms.

#### Survey carousel order

Admins can now control the order surveys appear in the portal and request-panel carousel:

* Open **Feedback Survey Settings** and click **Survey order**.
* Reorder **Request panel** and **Project panel** surveys independently via drag-and-drop or arrow controls.
* Order applies when multiple surveys are collectible at the same time; collection rules still control whether each survey is shown.
* Public-scoped surveys are not included — they are shared via standalone links or website embeds, not the portal carousel.

#### Other improvements

* Public frontend rebuilt with improved embed popup and score widget rendering.
* Live preview in survey settings.
* Server-side authorization hardening.
* SQL performance optimizations for collection and reporting.


---

# 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/users-guide/release-notes.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.
