Feature Requests

We value your feedback! You can vote for existing posts, add comments or add your own.
Allow a blank default for Yes/No fields
Most field types can be set with a blank default, but not Yes/No fields. In my use case, I'd like to force users creating a new record to affirmatively indicate the starting state of a Yes/No field. Marking the field as required doesn't achieve this because the field's default state is already either Yes or No, which means that validation doesn't flag the field as missing data when users try to save. Example: I have a Yes/No field called "Is a Contract Required?" This is a question where the answer is a binary, so I didn't opt to use a Single Select field. I also like the heightened visibility of the Yes/No field for grid and other views compared to the way Single Selects display. The field defaults to No because most of my records do not require a contract and, more importantly, because I have no "User Input Required" option for the default that would leave the field blank until I enter Yes or No when creating or updating a record. I'm entering data for a new record, and since the default for this field is No it becomes habit to ignore the Contract Required field, which is usually set to the correct option. Then I encounter an item that does need a contract. I should mark the Contract Required field as Yes, but because I've been effectively skipping the field for some time, I reflexively do so again. Now my record says it does not require a contract when it in fact does. I have automations keying off this field when it is set to Yes, and for this record, those automations do not run. A contract record is not created, assignments don't get made, notifications don't go out. We risk inadvertently proceeding without a contract for the work associated with this record.
5
Linked record, sub-items and checklist fields UX and UI tweaks
I have a few suggestions that might improve the UX and UI when it comes to the linked record field. Just a little disclaimer, I’m no expert in these fields, so all the following is based solely on my opinion. What if the linked record field behaved like a small grid view? (We kinda see that already in sub-items. But subitems aren’t a database and are exclusive to the record which is a huge drawback.) In summary, the field would be a grid view, filtering the records that are connected to the current record. So, we would be able to: • Create new linked records with one click • Edit properties without having to open the record • Select, copy, and paste one or multiple fields • Sort, group, highlight, or filter even further the linked records In fact, it would be awesome if all these features were applied to the subitems too. I hope I don’t sound pretentious, but I took the liberty to draw some ideas. The purple one is a visual representation of what the linked record field could look like with the functions I mentioned. The yellow one is the current UI to illustrate the visuals of these three fields, which have some similarities in usage but look completely different side by side. In the blue examples, I tried to make the visuals of the fields a little more similar by removing the color around the linked record field and the frame around the sub-items field (IMHO they make the visuals a little busy). Lastly, in the pink version, I tried to make them all really similar and using the visual from the purple one. I personally like #2 better. I’m probably the only one who gets "bothered" (not really, lol) by the different visuals in such similar fields. I think if they looked more consistent, it would be easier to find my way inside the record. Just to emphasize, I’m no expert at all, and you guys do a GREAT job. These are just suggestions that I think could make people's jobs a little bit easier, especially on the UX aspect (filters, grouping, etc.).
5
Load More