Hi 5d82e8f41e45

Thanks for solving this problem.

The anchor does redirect to the right place, but it takes about 5 seconds.

As mentioned below, this is not clear to users and causes issues.

Is it possible to optimize this script so that it opens faster?

Hi everyone,

The issue described on this ticket has been fixed. If you're still noticing any other issues with scrolling, please reach out or create a new ticket describing the issue and I'd be happy to investigate further.

Thanks,

Chris

5d82e8f41e45 you are correct, it works. it seems there was/is a significant delay, when is started scrolling (second+ ) but if to wait, then  it scrolls into correct position, But seems to work yes. thanks for checking it out.

Hi 77da2a39b46f, I just tried out what you mentioned – embedding a page in a Jira ticket that links to a heading, as well as to an anchor – and both scrolled to the correct location. Let me know if I may have missed a step in the reproduction.

The fix I mentioned a couple days ago has been rolled out, so scrolling should happen much faster now. If anyone is still running into issues, please leave a comment describing what you're experiencing. Otherwise, I'm planning to close this ticket in the coming days, as I believe the issue originally described in the ticket has been resolved.

2ff64bc9e115 For the latter, you have to make sure the anchor is BEFORE the heading, otherwise it cuts it off.

Hi 5d82e8f41e45
so with the anchor macro, loading works correctly for me (tested with H1 and H3 headings). However, it's difficult for me to explain to my users that they need to wait 1-3 seconds.
With the direct links to the headings, I do reach the correct spot on the page, but in 2 tests (H1), the heading was cut off, so it started just after the heading.

When copying a Heading link containing anchor and inserting this link into Jira ticket as Embeded confluence page doesn't scroll the confluence page into correct position but remains on top of confluence article. While manually adding an anchor point into confluence and adding that as a link opens the embeded confluence page in Jira in correct place where anchor references.

Hi everyone,

I'm a developer on the Confluence team and I recently fixed some issues around linking that I believe are related to this ticket:

• https://jira.atlassian.com/browse/CONFCLOUD-77822
• https://jira.atlassian.com/browse/CONFCLOUD-62589 

If I understand this ticket correctly, it sounds like the issue is that if you try to navigate to a link from one page that points to an anchor on another page, the navigation will happen but the page won't scroll to the correct location - it'll just remain at the top of the page. I believe the recent fix I made around July should've resolved any issues with not scrolling. If you're still seeing this behavior, try to give the page a few seconds to see if it eventually jumps to the correct location - it should. If not, please leave a comment letting me know.

That said, I'm now looking into the problem of having to wait a few seconds for the page to actually scroll, as this is obviously undesirable. I'm going to be pushing a change out shortly that should significantly improve this behavior, and I'll follow up with a comment when it's rolled out.

Thanks for your patience on this one.

Chris

There's actually another workaround. If you click "copy link" next to the title of a page, you'll notice that the url is quite different. If you attach the anchor to THAT url, it actually does link from other pages. Combine that with dynamic Go Links like go/your-page/anchor, and you're in business.

I haven't had such a good laugh for a long time. After 5 years, someone assigned a due date? LOL.  f7ae1d98cc50 - you just made a little mistake, the due date should be Sep/2042, that's the probably just the right time it will take Atlassian to find out how a hyper-link works.

The "Gathering Impact" is also laughable. Like you're trying to find out how many people are using hyperlinks? Oh dear, links, such a cool feature, it was invented only ~35 years ago. I don't know what kind of Impact are you gathering, but let me tell you a secret - I did (and so dozens of my colleagues) unsubscribed from all issues we created or watched on Confluence FOUR YEARS AGO. Not weeks, not months, years.

F O U R    F *   Y E A R S    A G O.

This is the only issue I keep watching out of pure perverse curiosity, if it ever gets fixed. But even if it gets fixed, it's absolutely not gonna change my opinion of Confluence as one of the most basically broken products being sold and Atlassian as one of the most inept, incapable and incompetent company still in operations.

44bb8b255fcc You're actually wrong with one thing - this issue has a workaround - as part of the link, you need to add screenshots to the other pages with the underlined title to which you're referring. That's the only reliable thing. Our docs are just full of screenshots of other docs...