# Feedback

Feedback is the screen for receiving the comments and improvement requests people come up with while using the product. Where open questions are the things you ask the stakeholder, feedback covers what arrives from stakeholders and users.

![PM on Rails feedback. Live operational comments in a list. Before: field comments never returned to the next request. After: they stay as material for the next improvement.](https://pmonrails.com/docs-img/feedback.png)

## What to send

From Send feedback, fill in the following.

| Field | What it means |
| --- | --- |
| Title | What the comment is about |
| Target screen | The URL or screen name. Where it happened |
| Ideal | What should be happening instead |
| Current | What actually happens |
| Steps to reproduce | The actions that get you to the same state |
| Other | Notes, an explanation of a screenshot, background |

Fields you leave empty are shown as "not filled in". They are never dropped just because they are blank.

## After it arrives

- **Filter by unanswered / in discussion / resolved** — Makes it easier to find the comments still waiting on you.
- **Keep the exchange** — Follow-up questions and answers can stay under the same piece of feedback.
- **Mark it resolved** — Mark it resolved once it is handled. You can move it back to unresolved if you need to.
- **Feed it back into requirement cards** — Anything that should be fixed as a matter of spec goes on to a requirement card, a requirement or a change request.

## Differences by role

- viewer (stakeholder) can raise feedback and reply to it.
- editor and above can mark it resolved, or move it back to unresolved.

## Next steps

- Take it forward as a defect → [Bugs and change management](https://pmonrails.com/en/docs/bugs-changes.md)
- Reflect it as a spec change → [Change tracking and diff checks](https://pmonrails.com/en/docs/change-tracking.md)

---

https://pmonrails.com/en/docs/feedback