> 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/turn-feedback-into-action.md).

# Turn Feedback into Action

### Link Feedback to Issues <a href="#link-feedback-to-issues" id="link-feedback-to-issues"></a>

Collecting feedback is only half the battle, acting on it is where the real value lies. Myra allows you to seamlessly turn customer insights into actionable Jira work items directly from your reports.

<figure><img src="/files/PD4QZ675X6Jvr8LvC20V" alt="" width="563"><figcaption><p>Feedback item actions</p></figcaption></figure>

#### Create a New Linked Issue <a href="#create-a-new-linked-issue" id="create-a-new-linked-issue"></a>

If a piece of feedback requires a brand new task, bug fix, or service recovery effort, you can create one without leaving Myra.

1. Navigate to the **Reports** tab and locate the specific feedback.
2. Click the **Actions** menu and select **Create linked issue**.
3. Fill in the required Jira issue details and create the ticket. The new issue will automatically be linked to this exact feedback item.

#### Link to an Existing Issue <a href="#link-to-an-existing-issue" id="link-to-an-existing-issue"></a>

If the feedback relates to a bug or feature request your team is already tracking, you can attach it to the existing work item.

1. From the feedback's **Actions** menu, select **Link to existing issue**.
2. Search for the target Jira issue using its **Issue Key** (e.g., SUP-123) or **Summary**.
3. Select the issue to establish the link.

<figure><img src="/files/z0xd4I2rVXG683NoXkCw" alt="" width="375"><figcaption><p>Link issues to feedback items</p></figcaption></figure>

#### Manage Linked Issues <a href="#manage-linked-issues" id="manage-linked-issues"></a>

Maintain complete control over how customer feedback connects to your Jira backlog.

* Open the **Actions** menu on any feedback entry and select **Linked issues** to see a list of all associated Jira tickets.
* Click on any linked issue from the list to jump straight to its details in Jira.
* If a ticket was attached by mistake or is no longer relevant, you can quickly **unlink** it directly from this same view.

<figure><img src="/files/I0mok3Pw9sQfAufmxh1e" alt="" width="375"><figcaption><p>Manage linked issues</p></figcaption></figure>

#### View Feedback on the Jira Issue View <a href="#view-feedback-on-the-jira-issue-view" id="view-feedback-on-the-jira-issue-view"></a>

The connection between Myra and Jira is bidirectional. Your agents and developers can instantly access the customer context behind a specific task or bug right from the Jira issue itself -no tab -switching required.

* Open any linked Jira issue and click the **Myra** button, situated directly beneath the issue summary.

<figure><img src="/files/GtFSj0TDwSZFG8UkHRjp" alt="" width="563"><figcaption><p>Click the Myra button</p></figcaption></figure>

* A dedicated panel will expand to display the exact scores and comments of all feedback submissions linked to that specific work item.

<figure><img src="/files/VMhuw1k4oRWmRsC0C7ic" alt="" width="563"><figcaption><p>Linked feedbacks</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/turn-feedback-into-action.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.