Ability to Set Form as Default New Button

[Chr1sG]

@danielbmarsh

My guess is that he doesn’t want to use the table on the database view.

I get that he doesn’t want to use ‘database view’ (for whatever reason) but I don’t understand what this has to do with how a form works.
There are loads of places where you can create an entity without using the db view, so I would say that db view is ‘avoidable’ irrespective of what you do with forms. but nevermind.

From his and your posts, is it correctly understood that you want to limit creation of an entity to always being achieved via a form?
And is this basically a way of achieving ‘required fields’ on entity creation?

We don’t currently have a nice way of making fields mandatory in all places where entity creation can occur, but I can see some other related topics:

Required fields on the layout

We have several types, where we need to be sure some fields are not empty. It would be great if we can mark fields as required OR create a validation rule if fields are empty (display an error message).

Creating "Required Field" Prompts

Just learned how to add these “Required Field” prompts. See example here: [image] Video Source: In Focus Project Planning - Part 2 | TrueBrow Use Case - YouTube Will update this post again but feel free to add the steps below

How to increase quality of the created tickets?

In the implementation I use now, currently, there is ability to create instantly e.g. features or bugs or other database entities. Leads to a lot of “one liners” because there is no such things as “create form”. I am looking into the ways to make creators fill in some mandatory hygienic attributes. What are the ways to make this happen? I see that buttons can be created, but then I would need to prevent everything created via other channels (e.g. lists of boards)? I am looking for an answer …

It is possible that the solution to the ‘required fields’ problem might be enforcing specific form view usage, but there might be other ways it could be solved.