I’m building an app for bug reporting that has multiple rich text fields (“steps to reproduce”, “expected behavior”, and “actual behavior”). I’d like a form view for this type that lets me enforce that users must fill out these fields in order to create a new a bug report.

Form View is implemented and released. Now you can add more granular feedback [image] November 17, 2022 / Form View heart_eyes, Timeline and Calendar relation Views Changelog Form View Finally you can create Form Views in Fibery and capture data from random peo…

There was recent mention about Forms not being prioritized because Fibery doesn’t feel it is important , but I wanted to express my opinion that I think Forms are absolutely critical to product team adoption. My reasoning: A core function of product teams is to manage external input As a developer…

I agree that native forms will be much easier to configure and use. We’ll re-think its priority. Why don’t you use Typeform + Zapier for example?

[image] mdubakov: Why don’t you use Typeform + Zapier for example? What does Typeform + Zapier give me that Coda + Integromat doesn’t? Either way I have to maintain consistency between the Fibery type, the automation platform, and the form, no matter what it is hosted through right? With Typ…

Not to mention using two third-party apps to achieve such a simple result is cumbersome and expensive.

Typeform / Tally / Jotform etc, can’t use internal app data. That’s a really common use case to use forms based on existing datas.

+1 for this as a much needed feature for collecting external inputs If / when you do implement forms I would really love to be able to prefill the form fields using URL parameters like Google Forms does . Also having hidden fields would allow for some pretty neat automations. For example I can have…

Form View implementation started today. We hope to release something in October. If you can describe your cases, like full flow with the Form View, it will help us to make better decisions. :face_holding_back_tears:

This is great news! In order of want: (required fields, hierarchical relations, same formula capabilities as automations/buttons, and multiple (linked) databases per form) Use Case: Simplifying Infrequent Complex Workflows (e.g. project setup) When logging a new project in Fibery, there is a natur…

[image] mdubakov: If you can describe your cases, like full flow with the Form View, it will help us to make better decisions. :face_holding_back_tears: Fantastic to hear implementation is underway for Forms. I’m happy to share my thoughts on use cases. In simple terms, I find there are two …

[image] mdubakov: If you can describe your cases, like full flow with the Form View, it will help us to make better decisions. :face_holding_back_tears: To me key features of a form would be ones that enable the user to complete a workflow in a self guided way. I want to be able to say “Hey n…

[DONE] Form View and required fields

Ideas & Features

mdubakov November 17, 2022, 12:49pm 25

Form View is implemented and released. Now you can add more granular feedback

Topic		Replies	Views
CHANGELOG: October 28, 2022 / Form View (experimental), View description, Hide Spaces, ClickUp sync Changelog	16	1191	November 10, 2022
November 17, 2022 / Form View 😍, Timeline and Calendar relation Views Changelog	20	1511	December 19, 2022
Entity view customization Ideas & Features	29	1005	July 23, 2026
Native JotForm Integration Integrations	6	1240	November 17, 2022
July 9, 2026 / Extra usage for automations and integrations, Forms restyling, Custom Apps improvements Changelog	9	354	July 16, 2026

[DONE] Form View and required fields

Related topics