A useful idea starts with a problem that can be reproduced.
The feedback portal prepares a structured request and explains how it moves from observation to a public decision. It turns neither a vote nor a form into a roadmap promise.
Current channel
The template can be copied without collection; the general brief can be sent only after compliant activation. No public voting portal is connected.
Choose the right path before writing.
Security risk
Publish no secret. Prepare a private, reproducible report.
Security procedureFunctional problem
Gather version, steps, result, and impact before using support.
Prepare diagnosisProduct improvement
Describe the moment, problem, and expected result without imposing a solution.
Copy the templateReproducible improvement proposal
addly IMPROVEMENT PROPOSAL 1. Work moment - Host product and placement: - Affected person or role: - Current task: 2. Observed problem - Steps: - Current result: - Frequency / impact: - Workaround: 3. Desired result - Success indicator: - Acceptable limits: - Data or permissions not to add: 4. Decision context - Relevant addly product: - Date or event motivating the request: - May I be contacted to clarify?
From request to delivery trace.
What the state means.
Is a submitted request accepted?
No. If collection is enabled and submission confirmed, it becomes an input to qualify, not a delivery commitment.
Does request volume decide priority?
No. Frequency, impact, product fit, risk, maintenance cost, and expected evidence matter together.
How do I know an idea shipped?
Only when a changelog entry links to the updated behavior and documentation.
Where should a vulnerability be reported?
Never in public. A private channel must be configured before launch; Security describes the expected procedure.
Propose the problem. Let the solution earn its place.
Copy the template, then open the brief with ‘Suggest an improvement’. Local copy always works; any compliant submission will never become a roadmap promise.