🐞 Bug Reporting in Limble – Is Anyone Else Frustrated?

Zisha

Hi everyone,

I'm an end user of Limble and wanted to open up a conversation around how bug reporting and issue tracking is currently handled.

Personally, I’ve had a pretty frustrating experience when it comes to reporting bugs. Most of the time, I have to submit issues through the chat feature, which:

• Feels clunky and time-consuming
• Often results in the issue being misunderstood or delayed
• Frequently gets labeled as “Product Feedback” even when the problem is clearly breaking functionality

I get that not everything is technically a bug, but if the platform doesn’t behave as expected, or if something was designed in a way that doesn't work in real-world use, that should count as a bug. Just because it was “intended” doesn’t mean it’s right.

💬 I’m Curious to Hear from Other Users:

Please feel free to answer any (or all) of these questions in your reply:

1. How do you currently report bugs or issues in Limble?
   (Through chat? Email? Feedback button? Something else?)
2. On a scale from 1–10, how easy is it for you to report an issue?
3. Do you feel like your reports are taken seriously and followed up on appropriately?
   (Any examples—good or bad?)
4. Have you ever had an issue dismissed as "product feedback" when it felt like a real bug?
   (How did that make you feel, and did it ever get resolved?)
5. Do you think the team at Limble fully understands how its features are used in day-to-day operations?
6. What changes or improvements would you want to see in the bug reporting process?
   (E.g. an in-app ticket tracker, clearer classifications, better support handoffs?)
7. Do you have any tips or workarounds that help you get attention on your reported issues more effectively?

Let’s make this thread a space for real feedback. Hopefully, if enough of us speak up, Limble will see the value in improving this part of the platform for everyone.

Thanks in advance!
A fellow frustrated-but-hopeful user