Currently, the new Jira Issue macro in Confluence Cloud only lists Jira sites where the user has access with the same Atlassian account (email address) as their Confluence site. This limitation prevents users from embedding issues from Jira sites that have a different userbase or are not part of the same Atlassian organization.

Request:
Please enhance the new Jira Issue macro to support connecting to and displaying issues from Jira Cloud sites that have a different userbase than the Confluence site, similar to how the legacy macro works via Application Links (AppLinks). This would restore flexibility for organizations that, for compliance, security, or structural reasons, maintain separate user directories or Atlassian organizations for Jira and Confluence.

Current Workarounds:

• Use the Same Atlassian Account: Ensure you are a user on both the Jira and Confluence sites with the same Atlassian account (email address). If your organization manages both sites, consider merging them under the same Atlassian organization and ensuring users have a single Atlassian account across both products.

• Use the Legacy Macro: If you must use different accounts, continue using the legacy Jira Issue macro (which relies on AppLinks). Note: Atlassian is deprecating legacy macros, so this is not a long-term solution.

Business Impact:

• Organizations with separate userbases for Jira and Confluence cannot use the new macro, impacting reporting, collaboration, and integration workflows.

• The deprecation of the legacy macro will remove the only current workaround, making this a critical gap for affected customers