Issue Summary

Right now, if the Jira Cloud coexists with the Confluence cloud application on the same site, the System Jira application will be set as the Primary, and there is no option to alter it.

In a situation where the customer would like to use the Jira application from a different cloud site or from DC, to fetch Jira work items onto Confluence via Jira issues macro, the Jira issues macros will always be pointed to the default application link System Jira, which is set as Primary.

Right now, the Primary label cannot be removed from the System Jira application link unless the Jira Cloud application is removed from the site where Confluence coexists.

Please provide a way to achieve any of the following approaches

• Ability to alter the System Jira application link status to remove the Primary tag
• Ability to remove the System Jira application even if the Jira application co-exists with Confluence Cloud on the same site

This would benefit customers who are willing to set any application link as Primary and use the sJira application from any site as the default on Confluence Jira issues macro (Both Jira Legacy and Jira issues macro)

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available