Hi @Pedro Siqueira ,
This is actually a known limitation when using third-party macros like Mosaic Tabs Macro inside Confluence Cloud.
This happens because
When someone is @mentioned in a comment:
Confluence sends a notification email with a link.
That link normally includes an anchor to jump directly to the specific comment.
However, when the comment is inside a dynamic macro (like Tabs), the macro content is rendered after the page loads.
Because of that, the anchor link can’t properly target the comment inside the tab.
Result → The page opens at the top instead of the tagged comment.
This is unfortunately a technical limitation of how dynamic macros render content in Confluence Cloud.
Possible Workarounds :
Here are a few practical options:
Use Page-Level Comments Instead
Instead of commenting inside a tab section:
Add the comment at the bottom of the page (standard page comment area).
Mention your colleague there.
These links work correctly and jump to the right comment.
Avoid @Mentions Inside Tabs for Important Actions
If the mention requires action, consider:
Mentioning the user in the main page body (outside the Tabs macro).
Or adding a short “Action Required” section outside the macro.
Raise with the Vendor
Since this involves a third-party app, the best long-term solution would be for the vendor to improve anchor handling.
You can:
Check the app listing in the Atlassian Marketplace
Contact the vendor support for Mosaic Tabs
Ask whether deep-linking to inline comments inside tabs is supported or planned
Why Atlassian Can't Fully Control This
Macros like Tabs use iframe or dynamic rendering, which can break native anchor navigation. This is not typically a core Confluence bug but an interaction limitation between Confluence and the app.
I hope this may help you out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.