You could search here (Jira Software / Server / Suggestions) to see if this feature has been suggested, and if so, vote for that change. That's worth doing, but don't hold your breath waiting for it to be fixed. They have a LOT in their backlog.
_ _ _ _ _ _ _
Another option to help avoid user error in this use-case would be to create a Jira automation rule which does it correctly each time. Unfortunately, there isn't a rule action to move an issue from one project to another. So if you're ok with a workaround...
The automation rule I'm suggesting would start with the "Manual trigger". This means users would select the rule name from the "More" or "..." menus on the specific issue. So naming the rule well is important, to allow your users to find and select it (perhaps something like "Move to XYZ" where XYZ is the destination project).
The rule would then use the "Clone issue" action to make a new issue in the destination project. This is also an opportunity to customize the "Summary" if you want, using Smart Values.
Finally the rule would close the original issue ("Transition issue" to Status "Done"). You could optionally add a comment including a link to the cloned issue.
If you're new to Jira automation, you could start here:
https://confluence.atlassian.com/automation/components-in-jira-automation-1141480614.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.