Hi,
Short statement of challenge: Custom Field configured as not Required but seek to make mandatory on a specific Project's Create Issue screen
I have a Custom Field with a Field Configuration where it is not a Required field so that it can be optionally used by Projects.
However I have one Project where I would like it's use to be Required.
My ideal solution would be to have the Create Issue screen for the Project require that field to be entered.
So my question is:
Is it possible for a Custom Field to have a Field Configuration where it is not a Required field, but force a Create Issue screen for a specific Project that uses that field to require that field to be set?
Thanks!
Give the two projects separate and different "field configuration schemes". In one scheme, make the field mandatory, in the other, it should be optional.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.