> For the complete documentation index, see [llms.txt](https://docs.released.so/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.released.so/guide/product/feedback.md).

# Feedback

{% embed url="<https://www.loom.com/share/1ba4a732b57e4f4c81696144db8af840?sid=d50e0ed2-a8e4-444a-803c-54216d5452bd>" %}

Released makes it easy to collect, manage, and act on customer and stakeholder feedback across your roadmaps. Once enabled, all feedback lands in a centralized inbox where it can be triaged, responded to, and linked to your Jira work.

## Enabling feedback

To enable feedback:

{% stepper %}
{% step %}
**Open the feedback settings**

Navigate to *Workspace > Settings > Feedback*
{% endstep %}

{% step %}
**Turn on feedback**

Toggle the feedback switch to enable feedback for the workspace.
{% endstep %}
{% endstepper %}

Once enabled:

* Users can comment directly on roadmap items via your portal.
* A *Give feedback* button will appear in the top right of your portal, allowing users to submit general feedback, not tied to a specific roadmap item.

{% hint style="warning" %}
Feedback is currently available only in the Product Hub. The option to leave feedback in embedded views will be available soon. You can [track the feature here.](https://hub.released.so/released/roadmap/ad0e75c1/issue/12258)
{% endhint %}

## Where Feedback Goes

All feedback in the Feedback [Inbox](/guide/product/feedback/inbox.md). Replies to existing threads do not create new entries but are displayed inline within the original thread.

## Linking Feedback to Jira

Feedback left on roadmap items is automatically linked to the corresponding Jira work item. For other feedback, you can manually link threads from the inbox to any Jira work item. This keeps your team close to customer needs and makes it easy to follow up when work ships.


---

# 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.released.so/guide/product/feedback.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.