To Be Able to Create Issues By JIRA Mail Handler Fingerprint

Problem Definition

When JIRA receives a mail to create issue from another JIRA instance, having X-JIRA-FingerPrint prevents JIRA to create issue and throws the below error in the logs:

Received message with another JIRA instance's fingerprint

For more detailed information you can refer to:
https://confluence.atlassian.com/display/JIRAKB/JIRA+Email+Finger+Print

Suggested Solution

To enable the administrator to have an option to be able to create issues. However, this might lead to loop issues.

This feature is to avoid loop and loop detection so we do not recommend to enable it, unless we get Atlassian Development Team idea about it.

Do note that Atlassian do not support customization as described on the documentation as outlined in our Atlassian Support Offerings. Please only try if you are confident on doing so and we strongly encourage customers to perform the check on test environment first before applying to production.

Explanation By Customer(In the comments):

The increasing number of JIRA instances, and how we'd like them to work together, raises an interesting use case for us:
Desired Outcome
What we'd like to do is create issues in our JIRA instance from another organisation's JIRA emails to us. We can't do that because our JIRA handler detects these emails as correctly belonging to another JIRA instance.
Steps:
Organisation A (OrgA) and Organisation B (OrgB) both have their own JIRA instances.
OrgA sends support request email to OrgB
OrgB JIRA mail handler detects email and creates issue (Issue Key ORGB-1)
OrgB sends JIRA issue notification to OrgA
OrgA JIRA mail handler detects email and create issue (Issue Key ORGA-1)
OrgA JIRA local users / groups can use ORGA-1 to track issue progress with OrgB without needing access to OrgB JIRA.
Actual Outcome
Organisation A (OrgA) and Organisation B (OrgB) both have their own JIRA instances.
Steps:
OrgA sends support request email to OrgB
OrgB JIRA mail handler detects email and creates issue (Issue Key ORGB-1)
OrgB sends JIRA issue notification to OrgA
OrgA JIRA mail handler detects email from OrgB and rejects it with the following error in the logs: "Received message with another JIRA instance's fingerprint"
No issue is created in OrgA JIRA.
This would be extremely useful because it allow users or user groups issue visibility and tracking with issues lodged with another organisation's JIRA.