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).

Released today. In the next releases we will make UI less obtrusive in all views [image] February 20, 2025 / police_officer Required Fields, Comments on Whiteboards, Asana integration, some permissions improvements Changelog This release is packed with several…

You could create a formula field that checks for empty fields, and returns a clear message: if(IsEmpty(Name),"❗ Name needed ❗","") You can then also create a view that lists the entities that need attention. OR You could create automation rule(s) that notifies the Created-by person (or Assigned-…

A bunch of related prior discussion of required fields, both in and outside the context of a “form view”: [image] [DONE] Form View and required fields Ideas & Features I’m building an app for bug reporting that has multiple rich text fields (“steps to reproduce”, “expected…

Thanks @Oshyan and @Matt_Blais for the links, but yes, it should be acknowledged that this is something that is currently lacking :frowning:

@mdubakov @Chr1sG is that still actual? We need some validation rules to communicate with users. For instance, we have a view with tasks. Each task should be connected to the release version. The view has a filter to show only tasks with a release (otherwise we handle them in the Backlog view). A ve…

Not really a solution, but a workaround would be to create a Rule that sets a default release date when the entity is created, so at least new entities would show up in your filtered view.

The release is a separate object in the space :frowning: We have like Task->Release. Maybe it makes sense to replace an object with a dropdown menu for now. But still, it’s a problem because we can’t validate fields.

Out of curiosity, what do you think the expected behaviour should be in the case that a user attempts to create/update an entity that does not meet the validation criteria? Should the user be prevented from creating/saving the entity in that state, or should the deficiency be flagged to the user wh…

It should be a validation message to the user. Like all modern crms do.

[image] Chr1sG: Should the user be prevented from creating/saving the entity in that state, or should the deficiency be flagged to the user whilst not preventing them? Yeah validation gets tricky when you have more than one required field on an entity without a defined “submit” action - how d…

[DONE] Required fields

Ideas & Features

Matt_Blais September 13, 2021, 2:25pm 3

Topic		Replies	Views
Conditional Required Fields - Workflow validation Ideas & Features	1	86	October 31, 2025
[DONE] Form View and required fields Ideas & Features form-view	24	4410	November 17, 2022
[DONE] Enforce unique entries + Data validation + Required fields Ideas & Features	12	296	May 8, 2025
February 20, 2025 / 👮 Required Fields, Comments on Whiteboards, Asana integration, some permissions improvements Changelog	24	589	February 24, 2025
Conditional fields in apps Ideas & Features	38	2701	September 18, 2025

[DONE] Required fields

Related topics