Short answer: at the approval moment itself, this isn't possible natively — and it's worth knowing why before you build around it.
Approval steps bypass workflow transitions. That's documented expected behaviour, not a bug: a validator or condition on the approval transition is not evaluated, so the approver can hit Approve with your required field still empty. There's a long-standing open suggestion to change this (JSDCLOUD-6988, open since 2018).
Forms don't close the gap either — approvers can't edit form fields during the approval stage. They can see what the requester submitted, but not fill anything in themselves.
So the choice is where you move the input to:
1. Before the approval. Atlassian's own recommended workaround is to split it into two transitions: one that validates the required fields, and a separate one carrying the approval step. Give the first transition a screen with your select list and a validator, and tick "Show transition on the customer portal" so the supervisor sees it. They then do two actions — make the selection, then approve — rather than one.
2. After the approval. An automation rule on the approved transition that creates a follow-up task or sends a form link. This does not make the selection mandatory before approving, so only use it if "before" isn't a hard requirement.
If the selection genuinely has to be mandatory and at the approval moment, option 1 is the closest you'll get without ScriptRunner-style custom validation, and even then the two-step shape stays.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.