We are using Coda as a bug tracker system but there is not a way to force the submitter of an entry to add required fields.
This results on empty fields on some bugs and engineers might not have enough context to fix those bugs.
Do other people have similar use cases where required fields are necessary?
I did this for several clients, and usually I built an abstraction atop the actual data table.
By that, I mean I made a dedicated single-row table with all the inputs, a validation formula that returns T/F, a validation message, and a button that copies data from the form into the data table and is only enabled when the form is valid.
Where it was less critical, I didnāt make an abstraction but simply provided a validation message + some indication (e.g. red background via conditional formatting) that some data was invalid or missing.
You could fake a āSubmit Bugā button that could check a checkbox column. If you set this button as disabled if certain fields are empty, it gives the illusion that the bug isnāt submitted. A table could be filtered to āBugs not submitted yetā or an automation could run every morning that sends a reminder to the creator of the row that some fields are empty.
Those are great hacks @Paul_Danyliuk and @BenLee. Thank you for sharing!
Even if there are workarounds, I think that there is opportunity for the Coda team to implement a feature that solves this issue at the core and makes it easier for Coda makers to create doc-apps.
I usually use @Paul_Danyliuk method - an input table/form with a button that copy the data to the āmainā table and is disabled if the required fields are empty or have incorrect data type (e.g - text instead of numbers).
I like to use detail view to give it a form-like feel but unfortunately conditional formating doesnāt work there Conditional formatting visible in card and detail view so I list the missing fields in the validation message.
I might share an example in a few hours, whan Iām back at my computer.
Anyway, you can add my vote for this feature 
Hereās an example
This is part of a doc Iām currently working on for my research lab (Iām a student), to track order_requests-purchases-inventory (the doc is still under construction - any suggestions are welcome 
)
This is a big need of mine, too. Similar use as @Raul_San_N.H you are describing - I have a lot of need for Coda that your excellent templates in the gallery are more or less designed to fill - bug tracking, lining up user feedback and cataloging to certain missing features, and a few others.
I think a good analogy here is when you fill in webforms in your everyday use of the internet, in particular shopping carts or sign ups on apps, you will frequently not be able to complete the process if certain fields are not filled out. They turn āredā at times when you hit āsubmitā so the user can go back and complete them.
And one particular way to use this that would be very helpful is to force a comment to be added to a row when an action is taken. Ideally the row would be set up for the comments window to āpop upā and require a comment before completing the action. This is very useful in the case of processes being run in Coda: You might require a comment when the status is moved to ādoneā or ācomplete.ā If you have a column for āstatus,ā and you could with automation require a comment before the final status was accepted, youād have a very powerful feature for end users to easily remember to notate what they actually did to close out a process.
I wrote about this in another thread here, too:
Really eager to see this feature, thanks guys!
Dear @ABp,
Although I didnāt have time to play around with the input from @Paul_Danyliuk,
I just want to make you aware of his post
Mega trick: Different "Expand row" layouts for the same row
I have a strong feeling that ānewā doors are opening 
One more vote for this one! Itās a really a much needed functionality. The input forms also work, but itās a lot of work if you add or remove fields from the table. Would love to see this functionality!
Now there seems to be a required field when creating the details layout but it doesnāt really work as expected.
It might be good if tables with required fields restricted the way new rows can be entered:
addRows and related formulas would fail if the required fields arenāt set properlythere may be some UX gremlins lurking around that path thoughā¦
Bumping this, as I now am building things that will need required fields.
This would also allow us to move away from Google Forms for sign-ups, feedback, and such.
This would also allow us to move away from Google Forms for sign-ups, feedback, and such.
Actually, if you are concerned about the forms: coda forms has required fields. I havenāt used a google forms form for years.
I am not saying we couldnāt use some more options for Coda forms, but required fields works just fine.
Is there any development for required fields in Detail view?
The best I could think of is Button (Open row) > Canvas row in dummy table > Embedded link to a published form in the canvas row. Works, but is kind of clumsy because of the sizing and all.