We need as well the possibility to make it required especially when agents create tickets for customers.
Several reports filter on customer request type!

100% agree with Michelle de Bruijns comment. Its very important to get sure the notifications are send correctly. Especially for SLA agreements or customer experiencing our services.
I found a solution to set it as default but this only works inside the cloud not for server installations... 
https://confluence.atlassian.com/jirakb/automatically-set-customer-request-type-when-issue-is-created-via-jira-1026039858.html

 Edit: 
Found an article about the same workflow for Server but this is not working in our environment.
https://confluence.atlassian.com/jirakb/customer-request-type-displays-no-match-in-jira-859463969.html

Is anyone using this?

We would also like to have this feature implemented, not only for the purpose of moving the issue: for some of our agents it is common to create tickets for their customers outside of the portal / Channel Jira. Although Customer request type can be made available on the Create screen, it cannot be made mandatory. Sometimes agents forget to set the field. As a result, tickets without a Customer Request Type are not visible in queues as expected by the service desk teams, and notification for ticket participants is failing in these cases. As a workaround we use automation rules....  Our agents need support in making these, and these rules are in constant need of maintenance. 

Making Customer Request Type mandatory in the Create screen form the Jira channel, would save us the work we have on automation rules, would lower the number of 'disappeared/forgotten' tickets and results in better notification for Participants. 

Hello,

We need this feature too as our customers can no longer see tickets if they are moved to other projects if the customer request type field is not set.

Regards,

Finally its taking attention ! 

Our team would like to have this feature implemented. When our SD Agents move tickets they often forget to also set the new request type, just clicking through the Move Wizard, that results in request type resetting to No match.

We would also very much appreciate the possibility to set this field as required. We are moving issues to different issuetypes (e.g. from Incident to Service Request) to use different workflows. We can't afford having complains from customers who cannot see tickets in the portal either.
EDIT: It turns out you can still see tickets in the portal when a wrong request type is set in the ticket, but the displayed fields do not change to the new types fields.

Yes Sir! it is Adaptavist Scriptrunner, Thanks for taking time and read my comment

Milan Ardeshana - what behavioural plugin did you use?

I have two projects Project A and Project B

Both projects have been configured using behaviourous plugin to have the field mandatory, as this field can't be marked as REQUIRED from field configuration.

Now when ticket gets created or edited, its enforcing to have value other than null.

Now we keep moving ticket so frequent between projects, atleast 100 tickets in a day. And in both projects new tickets have values but once ticket moves, person who moves the ticket is always in hurry and press next-> next -> next> and Move. In between screen he forgets to update the field customer request type as behaviourous not able to cover issue move event.

Problem we face due to this:
Out in customer portal those tickets are missing in customer account although customer has access to both projects and also when it comes to approval stages, because Request type is not defined, Approvers don't get emails as we use variable, ${request.url} ${request.status} ${approval.buttons} in customer notification where request is null because Person who moved ticket forgot to update value while moving ticket.

We need solution for this as we can't afford having complains of atleast 20 customers daily they dont see tickets they created in their account.