The rules in the new form builder are utterly unpredictable and loaded with bugs, as others have noted. At this point, it is largely unusable unless you don't have form rules.
Where do I go to find out what bugs are already reported before I start putting in support cases? I don't want to waste my or QB supports time with things already reported. I have already wasted hours on these forms.
I'm interested to see this info as well. I'm still struggling with pipelines and miss the option and simplicity of automations.
No such official list exists that I am aware of. This whole thing is embarrassing if you ask me. I wish we could have resolved all the issues with Pipelines before having to deal with another product upgrade and an even larger list of new bugs.
Here is a list summarizing bugs I've already submitted as a support case:
Other bugs or issues I have mentioned or discussed openly, but not submitted include:
Unfortunately, there are still more bugs than this.
The product is not usable for my organization until they resolve the most significant bugs. Such as #2, #4, #7, and #8 on my list.
------------------------------LorrieOriginal Message:Sent: 07-05-2023 23:58From: Drew VogeSubject: New Form Builder Rules - Where is the bug list?
Regarding Point #8 it is still not working for my need which I explained in feedback #301364:Subject: "New Form Rules - Copy Value from Formula Field to "Multi-select Text""If anybody look for similar thing I encourage to vote :)
This whole thing is embarrassing if you ask me. I wish we could have resolved all the issues with Pipelines before having to deal with another product upgrade and an even larger list of new bugs.
Original Message:Sent: 07-06-2023 10:12From: LorrieSubject: New Form Builder Rules - Where is the bug list?
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.
It's frustrating dealing with these form bugs. And important to understand there is a difference between Support Cases (specific to your organization and apps) vs. "Feedback" (which is applicable to all Quickbase Users and Apps).
If you login to your Quickbase account and click "My Apps" in the top-left nav, then stuck to the left side of the screen you'll see a small "Give Feedback" tab that flys out when you click it. From there, there is a set of icons at the top where you can jump over a full page view to review the list of things others have submitted … as well as, Quickbase's Status for reviewing or fixing the reported suggestion.
There you may also upvote others suggestions. I've attached a couple screenshots, which ultimately lead to:
------------------------------Brian SeymourOriginal Message:Sent: 07-05-2023 23:58From: Drew VogeSubject: New Form Builder Rules - Where is the bug list?
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.
@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.
Some time ago I asked Support (via case) if there is way to see status for my Bug.
They replied that I need to look for it in Release Notes 😁, as they are not sharing bug list with us :)
This makes everyones job harder - both at quickbase and for their users. Ive had many instances over the years where i've put in support cases, got scheduled with quickbase support, talked through it, only to be told its a known issue. If I could just search through known issues and see that it was already on a bug list and being worked on, neither of us would have wasted our time.
Just a heads up, I saw a number of "Forms 2.0" fixes in the Quickbase August 2023 release notes.