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

# Feedback

Feature requests and bug reports can be created by opening the 'Support' tab on the right side of the screen. (If this feature has been enabled by the AppControl administrator) After submitting feedback it can be reviewed and submitted to Blue Storm by any user with the Platform Administrator role. For each feedback item that is created a ticket is opened with Blue Storm support.

When submitting bug feedback make sure you provide enough information for support to be able to reproduce the error. At a minimum provide the following:

1. Which steps did you take before the error occurred? (Which page where you on, what did you fill in, what did you click?)
2. What was the last action you took before the error appeared? (what did you click, enter, etc.)
3. What did you expect to see / happen?
4. What actually happened?

If the bug is regarding a task, pipeline, release, policy, or anything else that can be configured, please send a screenshot of the configuration of that item so that support can re-create the configuration in our test environment.


---

# 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.bluestorm.io/support/feedback.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.
