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…

@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…

[image] Dimitri_S: how do you know when all the fields are ready to be validated? Indeed, the user does not want to be bombarded with warnings whilst he/she is in the process of creating/updating the entity. [image] Dimitri_S: I think that data should be created/saved but the invalid fie…

I think field specific highlighting (that overrides color coding) would be a must for this type of validation, otherwise it would a) complicate/collide with existing color coding and b) be ambiguous to identify what’s causing the failed validation As a bonus, field specific highlighting (to indicat…

Just wanted to jump in here and say that I am still eager for simply required fields, like “business area” in a task if you want to make sure your team always has to label what they are doing. With today’s release of [DONE] Form View and required fields , I realized that I don’t think that actually …

I think that the feature of required fields is very important and should not be left up to a ‘workaround’.

[DONE] Required fields

Ideas & Features

mdubakov February 20, 2025, 12:39pm 23

Released today. In the next releases we will make UI less obtrusive in all views

Topic		Replies	Views
Conditional Required Fields - Workflow validation Ideas & Features	1	106	October 31, 2025
[DONE] Form View and required fields Ideas & Features form-view	24	4544	November 17, 2022
[DONE] Enforce unique entries + Data validation + Required fields Ideas & Features	12	343	May 8, 2025
February 20, 2025 / 👮 Required Fields, Comments on Whiteboards, Asana integration, some permissions improvements Changelog	24	651	February 24, 2025
March 5, 2026 / 🙈 Hide Entity Views with rules, Specify which Entity View to open by default for a user, Validation rules on Create Changelog	27	662	August 24, 2026

[DONE] Required fields

Related topics