How to make a required field

Maggie Stearns

When transitioning from one state to another (For example from "In Progress" to "Resolved"), I have a "Resolve Issue" screen. I would like one of the custom fields on that screen to be required.  

My choices for implementation appear to be these two choices:

1. Create a condition on the transition that prevents transitioning if that field is not populated.
2. Create a validator that gives an error if that field is not populated.

I don't like #1 because the user will not necessarily understand why the "Resolve" transition button does not appear for them. #2 is OK, but then the users are asking why there is no red asterisk next to those required fields when they enter the screen. I don't want to make them required in the field scheme since they are not required until this point in the workflow.

 

Any other possible ways to implement this?

Joe Pitt

I don't believe any of the plug-ins that will make a field required on a transition puts the asterisk next to the field. You can get around it by including the asterisk in the field name if it really bothers your users. The lira-suite-utilities plug-in will pop a message it is required if they didn't fill it in when clicking to complete the transition. I've never had much push back from the users as long as they are told in training about the behavior.