Jira incorrectly allows required fields to be blank after splitting the issue

Question

After splitting the issue, on split issue few fields are missing, is it default feature in jira ?

Bill Sheboy · Answer

Thanks for confirming that.  Then I suggest you ask your site admin to submit a defect to Atlassian Support for this symptom: https://support.atlassian.com/contact/#/

unknown · Answer

@Bill Sheboy  Thanks for responding , yes required fields are missing on the split issue.

Bill Sheboy · Answer

Hi @[deleted]

I found an open defect for this issue for the cloud version, but not for server:

https://jira.atlassian.com/browse/JSWCLOUD-18121

My questions would be: If these fields were required prior to the split, how are they empty?  Or, is splitting somehow clearing the fields?

Best regards,

Bill