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?

[Dawn Cooper]

And  thanks Nic! good to hear from you :)  

[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.

[Dawn Cooper]

oh, we used behaviors since we had trouble making a field required on one screen but not another within the same project. Users would get an error stating the field was required but it was not on the screen. We were trying to use the field configuration screen then to make a field required.  Any suggestions?

[Nic Brough -Adaptavist-]

I'm afraid not.  The "move" function has nowhere to hook custom field checks into it - it only looks at the field configuration for the target issue type, and provides no insertion point for any code.

[Satya Boddu]

Hi Nic,

Will this be the same result if we move a ticket from say, project A to Project B?