Required Fields are not being enforced when moving to a new issuetype

Dawn Cooper

We are using Behaviors to make several fields required on some issuetypes in one project. We you move a ticket from one issuetype to another these required fields are not enforced. For example, issuetype A does not have the some of custom fields that issuetype B has. Some of these additional custom fields are required on issuetype B. When the issue is moved from type A to type B, the wizard does not give the option to define these additional fields, regardless if they are required on issuetype B or not. How do I fix this?

Nic Brough -Adaptavist-

This is because Behaviours are not making fields required as far as Jira is concerned.  They tell the browser to do it, not the server.

There's nothing you can do about this, the fields are not really mandatory.