Deleted.
While I agree it is important to remember the different between a Support Case and Feedback, it's also important to remember the difference between a bug and feedback. Perhaps in the interest of time, the previous post confuses this a little.
Feedback insinuates a suggestion to make the product behave differently than it currently behaves. You should not submit a Bug here simply for the purpose of allowing other users to see it within the Feedback system. A Feedback example: in the New Forms, I believe some great feedback is that the embedded Report feature should not display the large space-consuming button and search widget by default. The user should be able to disable it.
Bugs are issues with the software and underlying code or workflows, and should typically be submitted as a Support Case inhibiting the user from using the software platform. We shouldn't really have to provide Feedback for a bug, as it should be addressed and fixed ASAP by the Product Development team. For example, some of the Form Rules in the New Form become corrupted with a "white screen of death" that cannot be recovered from, and this make the product essentially unusable of this happens.
The previous post might almost be suggesting that a Support Case is not applicable to all Quickbase Users and Apps, while that couldn't be further from the truth. The bugs I have submitted through the Manage Cases link are applicable to all users of the New Form product, and were quickly acknowledged. Just because all other users cannot see my Cases does not mean they aren't applicable to all users - since QB will ideally fix these bugs I submitted for ALL users. But you can't track the status of bugs I've submitted with the design of this system.
@Joel Hikock fair points.
I'll go ahead a remove my previous post to avoid further confusion. I was under the impression that is how QB preferred to receive feedback (both bugs and non-bugs) during the Empower conference. However, we'd need to find the recordings of the Empower sessions to confirm.
So at this time, I'm not aware of a comprehensive public list known issues or bugs list like we'd find on GitHub.
Providing a LINK on the NEW FORM when in form edit mode that takes one to a list of KNOWN BUGS would be helpful to new form designers. This would help them decide if the new form is useful in the context they are creating or not.
It would also save significant troubleshooting, consternation, and ultimately product frustration because it helps form editors save time figuring out why an expected behavior isn't happening.
