When cloning an issue, Jira will copy the data of a custom field over from the original issues state at the time of the clone.

Since cloning an issue extends an issue creation in a fashion, it would be helpful to consider the default value of a field that is set on the initial issue creation, which can help avoid data discrepancy issues in the case of automation that may require those default field values.