How to make custom field mandatory using Jira automation

[Priya]

If one of the custom field equal to certain values then we want to make 2 custom fields as mandatory.Whether it's possible to achieve using Jira automation

[Marcin Wiktor]

Not sure if this is the best approach but it works:

On a path transition you can make 2 grouped sets of conditions:

1. Custom field value = [option 1]

2. (set "All of the following conditions" on the top of the group) Custom field value = [option 2] AND Custom field 2 IS NOT EMPTY AND Custom Field 3 IS NOT EMPTY

[Mykenna Cepek]

Very often, the desire to have required fields comes into play when transitioning issues from one Status to another. In other words: when an issue moves through a part of the Workflow, we want to be sure these fields are filled in.

In that case, configuring this on the workflow, as @Marcin Wiktor suggests, is the preferred approach. Use "Conditions" and "Validations" on that step of the workflow. This will ensure that fields are set as desired, or prevent the issue from transitioning to the next Status in the Workflow.

More info on Workflow configuration (see "Conditions" and "Validators"):

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

Automation cannot "make a field required".