Feedback
Give the product team a concrete signal about what should improve.
Give the product team a concrete signal about what should improve.
What this feature is for
Feedback captures product observations, friction, and requests with enough context to become actionable work. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
The route, behavior, expected result, and any safe evidence or reproduction detail.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Describe what happened, what you expected, include the route and plan context when relevant, and submit one issue per report.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
A useful feedback record preserves category, message, route, timestamp, and workspace context without including secrets. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Never include credential values or customer data. Redact identifiers and link a safe report or error code instead.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Feedback alongside Activity and Help when the product behavior itself is the issue. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.