Jira can link to Confluence pages via Application Links and provide a native “Link Confluence page” experience.
However, Confluence Whiteboards are not recognized as first-class link targets:

• Pasting a Whiteboard URL in the “Confluence page” link dialog either fails or redirects to the space home page.

• Users must instead add the Whiteboard URL as a generic web link / Smart Link.

This leads to several limitations:

• Users cannot manage Whiteboard links in the same way as Confluence pages (e.g. in the “linked Confluence pages” panel).

• For cross-site scenarios (Jira site A – Confluence site B linked via Application Links), Whiteboards still cannot be treated as native Confluence entities from Jira’s perspective.

• Teams lose a consistent user experience between pages and Whiteboards, even though Whiteboards are part of Confluence.

Requested improvement

• Treat Confluence Whiteboards as first-class Confluence content types in the Jira–Confluence integration.

• Allow users to:

• • Select and link Whiteboards from the “Link Confluence page” dialog in Jira.

• • Correctly resolve a Whiteboard URL to the Whiteboard itself (not the space home page).

• • Use this both for same-site and cross-site (different Cloud instances) integrated via Application Links.

This would make Whiteboards usable as a true extension of the Jira–Confluence workflow (e.g. ideation and discovery in Whiteboards, tracked work in Jira), with a consistent linking model.