Conditional Required Fields - Workflow validation

Ideas & Features
1

I’m not sure if this has been articulated anywhere. With required fields being a thing, I thought it would be appropriate to create conditionally required fields.

These would occur in a few situations ordered by most important.

Required field by state. During a state change new fields might become required. For example a resolution might be required when closing a bug.

  • I image the UI could be similar to how required fields work when creating a new entity.

Sometimes Required Fields. During some workflows users when a user inputs some options it requires another field to be filled out. For example if selecting an “Other” option in a single select field it requires a “Describe” text field to be completed.

  • This one is a little trickier as Fibery does not have save states.
  • One way I see this working is to tie these to a state change. For example this field is required if this condition is met to advance this entity to specific state.
2

An alternative approach that could work (for us) is an ability to make it visually very conspicuous that there is a validation error both in entity view, list/board and other collection views without having to configure every view. Maybe something like a specially designated field that gets rendered next to the entity name. Then an automation can set it its content to, say, :red_exclamation_mark:, or the field itself can calculate its content using a formula.