RFC-136: Forge staticView Macro for Confluence, Connect Migration & Feedback

So let me get this straight… we can inject ADF with all sorts of links (that can include query string data egress) in static macros, and it will be A-OK for Runs on Atlassian and won’t even show any type of warning message to the end-user, but customer-managed egress is not on Runs on Atlassian because it might contain query string data egress (see Please help us shape the "Runs on Atlassian" roadmap for 2026 and beyond - #9 by HeyJoe)?

It would be nice if Atlassian can be consistent with regard to Runs on Atlassian requirements.

cc: @HeyJoe