How to Submit a Feedback (Bug, Feature, or Enhancement)

1. Use a Clear Title
Keep it short but specific.

• Bad: Form Builder Performance Improvement Request

• Good: Form Builder – Form needs multiple saves before submitting

2. Fill Out These Three Sections

• What is the problem or request?

  Example: When I add data into the Dynamic Table, I have to save multiple times before it sticks.

• Why does it matter?

  Example: This slows down form completion and causes mistakes if someone forgets to save twice.

• What do you expect instead?

  Example: Saving once should capture all the table data.

3. Add Supporting Evidence

• Screenshots: Take a screenshot and highlight the issue.

• Short video (30s max): Record your screen while reproducing the bug or showing the workflow step.

• Links: Add any relevant dashboard, doc, or workflow link.

🟥 Example: Bad Practice

Form Builder Performance Enhancement
- Forms requiring multiple saves before submission
- Dynamic Table (Search from dropdown functionality)

Too vague, missing why it matters, no screenshot or video.

Example: Good Practice

Title: Form Builder – Multiple saves needed for Dynamic Table

Problem or Request: I need to save 2–3 times before the Dynamic Table data is captured.

Why it Matters: This slows down my work and risks losing data if I forget to save multiple times.

What I Expect: One save should capture all the data.

Evidence:

• Screenshot attached: dynamic-table-save.png

• Quick video: loom.com/share/12345

Key Notes

• Always attach at least one screenshot or video — words alone are not enough.

• Be clear about the impact on your work (time wasted, errors, blockers).

• Use plain language. No need for technical details like “steps to reproduce” unless you know them.