BUG: When in Page Edit mode the "Copy link to heading" feature puts the wrong link in your clipboard

Question

When editing a page in Confluence Cloud, the "Copy link to heading" feature seems broken (unless I am missing something). It gives you the "edit-v2" version of the link, rather than the saved-page version of the heading link. The user has to know to copy the heading link before they go into Edit mode, otherwise they will save their page with Edit links, not navigable heading links. This is not a good workaround.

For example, it should put this in your clipboard:

(mysite).atlassian.net/wiki/spaces/(spaceKeyID)/pages/(pageID)/(pageName)#(headingName)

But it actually puts this into your clipboard:

(mysite).atlassian.net/wiki/spaces/(spaceKeyID)/pages/edit-v2/(pageID)...

Steps to reproduce:

1. Create and save a new Confluence page with at least one heading

2. Edit the page, go to that heading and click "Copy link to heading" (notice, it puts the wrong link in your clipboard, when it should give you the non-edit version)

Risk to User / Threat to Product Value:

If the user doesn't realize this (which I didn't until I had create a bunch of pages with bad links) then their links will actually open Edit mode and not navigate to the heading as intended. This manifests itself as a bigger risk if you work in a high-trust environment and allow many editors in your Confluence space.

Note: We've reported this bug to Atlassian, but let me know if there's a better workaround/way I can make this not a pain. Thank you.

Benjamin Greiner_pyt0lt · Answer

Yes please fix this. Apart from the "every hit from autocorrect makes the editor jump to the next line" bug, this is the most painful oversight in Confluence currently.

Kimberly O'Toole · Answer

Here is the link to the ticket for this issue:  https://jira.atlassian.com/browse/CONFCLOUD-79486

Levente Ambrus · Answer

On one hand the workaround doesn't work properly because clicking the link does not just scroll down to the link but calls another page instance and the scroll only happens on that page.

On the other hand the workaround doesn't work in many cases. Often the link is like this, where the workaround must include deletion of the draftShareId as well:

(mysite).atlassian.net/wiki/spaces/(spaceKeyID)/pages/edit-v2/(pageID)?draftShareId=(someId)...

A new improvement is the TOC Zone (table of contents that displays only content being within its body). Links to any headings within TOC Zone DO NOT WORK at all.

I used internal cross-links and anchor links earlier and they worked fine. I did miss the links to headings, though.
While developing this user-friendly feature is a great improvement, this bug makes using internal links completely unusable.