Submit feedback

How to share ideas, report bugs, and request features on a feedback portal: find the portal, check for existing posts, write a clear post with images or video, and what happens after you submit.

JM
James Morton
Written By James MortonLast updated 8 days ago

Share your ideas, report bugs, and request features through the feedback portal.

Find the feedback portal

Your organization's feedback portal is typically at:

  • feedback.yourcompany.com
  • yourcompany.quackback.io

Look for a "Feedback" or "Feature Request" link in the product you're using.

Browse existing feedback

Before submitting new feedback, check if someone else has already requested it:

  1. Search - Use the search bar to find related posts
  2. Browse boards - Look through relevant boards
  3. Filter by status or tags - Use the filter dropdowns to narrow results by status (e.g. Planned, In Progress) or tags
  4. Check the roadmap - See what's already planned

Tip: If you find an existing post, vote for it instead of creating a duplicate. This helps prioritize requests.

Create a new post

1. Choose a board

Your team sets up the boards, so the names depend on your workspace. Pick the one that fits your feedback. Common examples:

  • Feature Requests - New functionality you'd like to see
  • Bug Reports - Issues you've encountered
  • Integrations - Connections with other tools
  • Documentation - Improvements to guides and help

2. Write a clear title

Your title should be:

  • Concise - One sentence summarizing your request
  • Specific - Include key details
  • Searchable - Use common terms others might search for

Good titles:

  • "Add dark mode support"
  • "Export reports to PDF"
  • "Slow loading on dashboard with 1000+ items"

Avoid:

  • "Feature request" (too vague)
  • "This is broken!!!" (not descriptive)
  • "I think it would be really great if..." (unnecessary preamble)

3. Describe your feedback

In the description, include:

For feature requests:

  • What you want to accomplish
  • Why it's important to you
  • How you currently work around it (if applicable)

For bug reports:

  • Steps to reproduce
  • Expected behavior
  • Actual behavior
  • Browser/device information

For all feedback:

  • Context about your use case
  • Examples if helpful
  • Screenshots or screen recordings

4. Submit

Click Submit to publish your feedback.

Write your feedback

The post description uses a rich text editor. You can format with headings, bold, italic, lists, links, inline code, fenced code blocks, and emoji. Markdown shortcuts (e.g. **bold**, # Heading) are recognized as you type.

Mention a teammate or another user

Type @ while writing to mention a team member or another portal user. A typeahead picker appears as soon as you type the character; keep typing to filter by name, then pick from the list with the arrow keys and Enter, or click.

Mentioned users get an in-app notification and an email (if their workspace settings allow). The mention renders as a chip with the person's current display name, and hovering a chip shows their avatar and join date.

Note: Mentioning someone only notifies them about the post you're writing. It doesn't subscribe them to the post. They choose whether to follow it from there.

Embed images and code

  • Paste or drop images and videos directly into the editor while signed in. They're uploaded and hosted in your workspace. See Images and file attachments for types and size limits.
  • Use the slash menu (/) to insert headings, lists, code blocks, tables, and dividers.
  • Type three backticks followed by a language name (for example ts or python) to start a fenced code block with syntax highlighting.

After submitting

Track your post

Your post is now visible to:

  • The product team
  • Other users (on public boards)

You'll receive updates when:

  • The team responds
  • Status changes (planned, shipped, etc.)
  • Others comment

If your post is pending review

Depending on the board and workspace settings, posts from non-team members may be held for approval before they go public. A held post is visible only to you until a team member approves it. You'll get a notification when it's approved or rejected.

Vote for your own post

Your vote is automatically added when you submit.

Edit your post

To edit a post you submitted:

  1. Open your post
  2. Click the three-dot menu (if available)
  3. Select Edit
  4. Make changes and save

Note: Editing may be time-limited depending on workspace settings.

Delete your post

To delete a post you submitted:

  1. Open your post
  2. Click the three-dot menu (if available)
  3. Select Delete
  4. Confirm deletion

Note: Deletion may be restricted based on workspace settings.

Notifications

Control how you're notified:

  1. Click your profile avatar and go to Settings, then Preferences
  2. Toggle email notifications for:

    • Status changed
    • New comment

Unsubscribe from a post

To stop receiving updates for a specific post:

  1. Open the post
  2. Click the bell icon
  3. Select Unsubscribe

Or use the unsubscribe link in notification emails.

Tips

Be constructive

Frame feedback positively:

  • Focus on the problem, not blame
  • Suggest solutions if you have ideas
  • Remember there's a team reading this

Provide context

Help the team understand:

  • Your role (developer, designer, user)
  • Your use case
  • How often you encounter this issue

Check back

Look for responses from the team:

  • They may ask clarifying questions
  • Share status updates
  • Explain decisions

Engage with others

Support the community:

  • Vote on posts you agree with
  • Add helpful comments
  • Share your workarounds

Common questions

Why can't I see my post?

Your post may be:

  • On a private or restricted board
  • Held for review - Some boards or workspaces hold posts from non-team members for approval. A held post is hidden from other users, but you (the author) can still see it on the post detail. You're notified when a team member approves or rejects it.
  • In a different board than expected

Why do I need to sign in?

Authentication helps:

  • Notify you of updates
  • Track your votes
  • Prevent spam

Can I submit anonymously?

It depends on two layers of settings:

  • Workspace level - Your admin can require sign-in for all submissions by turning off the Allow anonymous interaction setting. When it's off, voting, commenting, and submitting require an account everywhere.
  • Board level - Each board sets who can view, vote, comment, and submit. Board access is Everyone, Signed-in users, Specific segments, or Team only. Submitting has its own permission on each board.

Viewing, voting, commenting, and submitting are gated independently per board, so a board you can view may still require sign-in to submit. If you see Please sign in to submit feedback, sign in first.

Was this helpful?

Your feedback shapes what we write next.