Jira Issue/Filter macro does not default to System Jira when other instances are linked on application link

Issue Summary

Jira Issue/Filter macro does not default to System Jira when other instances are linked on application link. This happens when there's an external Jira instance set as Primary and even after removing this instance, this behavior will persist with non-primary external instances.

Steps to Reproduce

1. Create a new instance with just Confluence;
2. Link 5 external Jira instances > Make one of those the primary one by clicking ... on the right-hand side > Make Primary
3. Enable Jira on this instance;
4. Create a Jira Issue/Filter on this instance - The macro will not default to the system Jira. (if System Jira is correctly selected follow the next steps)
5. Remove the Primary instance from application links.
6. Create a Jira Issue/Filter on this instance - The macro will not default to the system Jira.

Expected Results

• Jira Issue/Filter Macro to default to System Jira

Actual Results

• Jira Issue/Filter Macro will continue to default to external instances even though the Primary external instance was removed.

Workaround

Remove all application links from this instance and reassociate them again. This way when you create a new Jira Issue/Filter macro it will correctly default to System Jira