Validators - one of three fields can't be empty

[Lucas Minhones Mota]

We use 3 custom fields on a same Issue Type(named Problem) but with different Request Types.

Request Type: Micro > CustomField_1
Request Type: System > CustomField_2
Request Type: Infra > CustomField_3

When I try to set up a validator where one of these fields cannot be empty even if one of them is not blank, the dev cannot transition the issue to done.

Is there a way to do it using validators and the request type fields to trigger the notification only if all three fields are empty but if one of them is not, let ithem be able to transition?

[Ste Wright · Accepted solution]

Hi @Lucas Minhones Mota 

Natively, I don't believe you can do this - validators are checking that during the transition, the field's are being modified/populated, so it's all or nothing

Alternatives include...

• Conditions: Use these to decide if a transition is visible or not, based on one of the fields being populated. Conditions can be "all", "any", or a combination of the two, allowing for more flexibility
• Automation: Use an Automation rule to check if the fields are populated, and if not, reverses the transition to the previous Status. You could also use Automation to send a custom notification at the same time.

^ This is assuming the fields are populated before the transition, rather than during.

If it is a validator you need, I'd check out what options exist on the Marketplace instead, and trial if they can help you!

Ste

[Lucas Minhones Mota]

Thanks Stephen, using conditions worked for us.

It would be nice if we could use those combinations with Validator too, cause we can set an error message for the user.