Hi folks and t.leuoth526131402 sebastian.butterweck2 michael.mohr.ext1418337783 james.leighs1 reminder 82e5399ae2f4

Confirming that this fix was backported to the 7.4 LTS; apologies that this ticket was not updated at the time. The Fix Version/s has now been updated to include 7.4.8. If you're running the Confluence 7.4 Enterprise release, a fix for this issue is available in Confluence 7.4.8, which you can find in the Download Archives.

Thanks

Makisa | Senior Product Manager, Confluence Server and Data Center

Apologies, I have missed these more recent comments. We are going into the weekend here in Sydney, and I will follow up with the team as to the state of the fix on Monday. Thanks for your update 82e5399ae2f4 I will try and confirm this.

We've installed 7.4.8 LTS, and it seems that the bug is fixed in that release, although nothing was mentioned about it in release notes. Continuing to watch on 'problematic' documents and hoping the bug has gone.

Didn't Atlassian always mention "Don't f... the customer"? But what else then that is this topic. First Atlassian support states that there will be a backport soon to 7.4 and then now for more then 3 month there happens nothing. Shame on Atlassian!

When will the fix for 7.4.x LTS be released?

When will the fix for 7.4.x LTS be released?

More than 10 weeks ago Makisa Appleton from Atlassian promised that the fix will be back-ported to next upcoming Minor 7.4 LTS release. Was this meanwhile done, as there where intermediate LTS minor versions of 7.4 released since begin of March?

Or was this only a Answer from Atlassian at the beginning of March to keep customers silent and hoping that they don't come back to this issue after a while?

Backport to 7.4.x would be highly appreciated ... 

Is there a fix for Confluence 7.4 (Long Term Support release)?

Hi everyone

We've been doing additional testing to ensure that the fix can be backported safely to the 7.4 LTS. All going well, we are expecting that it will be included in our next 7.4.x bug fix release. There will be a further confirmation message added as a comment when this version has been released with the backported fix. Thanks for your patience.

markus.benda the next LTS has been confirmed as 7.13 and we are targeting FY21 Q3. Please see the Community post for more information.

skairys124192546 I hope you are enjoying the Confluence Cloud experience! If you are creating pages with the new editor, then you will not experience this issue and you can convert any previously created pages to the new editor. Please note linking functionality is currently different in Confluence Cloud and the team are working on CONFCLOUD-69198. /cc megan@atlassian.com

Thanks
Makisa | Senior Product Manager, Confluence Server and Data Center

Hi, Can you please provide any update on backport of this fix to the current version 7.4

Meanwhile we found out that we also are facing this problem in many pages. As big Enterprise with a 10000 user DC license we are also only using LTS releases.

So we also need a backport of this fix to the current LTS Version 7.4 as this bug corrupts our date it should hopefully also be clear to Atlassian that this fix really needs a backport to LTS! Otherwise I would ask ourselfs why we are paying so high subscription costs (more then factor 10 in comparison to 10000 user server maintenance costs 3 years ago)

I am also still interested in a LTS bugfix for this. We still encounter this issue in our Confluence instance.

Hi Atlassian, any new informations about adding this bugfix in next release of LTS? When do you plan to release the next LTS version?

Hello again,

TO repeat my question from earlier this week:

>>Does anyone know if this bug exist in Cloud? We recently migrated from SERVER ---> CLOUD and wondering if our users will be exposed to this bug. If they are, what is the "use case" they'd need to avoid - I need to pass on this info to our stakeholders. Thanks. <<

Hi everyone

Thank you for your comments requesting this to be backported to the LTS. I will discuss the feasibility of doing this with our team.

Thanks
Makisa | Senior Product Manager, Confluence Server and Data Center

Hi Atlassian, we need this bug fix also in the last LTS Version. Actually we use 7.4.4 (updated from 6.13.11 to 7.4.4). We only use LTS versions, which should have the best quality!!! We use the anchor very often. Links to anchors are broken from "#anchorname" to "pagetitle#anchorname". Please add this fix to LTS Version. Thank you!

Hi, does anyone know if this bug exist in Cloud? We recently migrated from SERVER ---> CLOUD and wondering if our users will be exposed to this bug. If they are, what is the "use case" they'd need to avoid - I need to pass on this info to our stakeholders. Thanks.

Bump on DavidP's comment - are there any plans to backport this into the Long Term Support release?

Hi ahmed.alaghbari and mig899012568,
Thank you for reporting this issue. We have a separate Jira ticket for tracking it here: https://jira.atlassian.com/browse/CONFSERVER-60444

Regards,
Alex K (Developer at Atlassian)

Yes, anchors don't work anymore. It seems related to the anchor macro. If you create the anchor using the HTML macro, the link works.

Hi,

I believe this fix has introduced a regression in same page anchors. To reproduce:

1. Create a long page (you can use Loremipsum macros) and add an anchor at the bottom of the page with the name bottom.
2. Scroll back to the top of the page and insert a link to the anchor with

   [#bottom] or [title#bottom]

3. Save the page and click on the link to the anchor.

Expected behaviour:

1. Clicking the link takes you to the bottom of the page where the anchor is.
2. The resolved anchor link should be http://myconfluence.com/display/KEY/title#title-bottom.

Actual behaviour:

1. Clicking the link doesn't scroll down to the same page anchor.
2. The resolved anchor link is http://myconfluence.com/display/KEY/title#bottom.

Workaround:
You can "trick" the link resolver to create the correct anchor link by using the following link syntax

[#title-bottom]

It should be noted that links to the same anchor from different pages still work as expected, only same page anchor links seem to be broken.

Thanks for looking into this. We hope this can be fixed and not get carried over to 7.9.x.

Best regards,

Ahmed Al-Aghbari

Hi, 

will you backport this issue to the Long Term Support Release?

As the other persons mentioned it is a big dealbreaker if you can't really copy a page and have to deal with breaking links. Furthermore this behaviour is difficult to explain to our users. Since there is no easy workaround (collaborative editing is essential in the current situation where teams are separated in their home offices) it would be great if you would fix in the next LTR bugfix release.

A fix for this issue is available to Server and Data Center customers in Confluence 7.8.1
Upgrade now or check out the Release Notes to see what other issues are resolved.

Hi mappleton@atlassian.com, 

I am so exciting to see that case in status "Waiting for release". 

Cheers,

Gonchik Tsymzhitov

Hi everyone

Thank you for your feedback and comments on this ticket. I understand that this longstanding issue is frustrating and difficult to work with. I have bumped up the severity and also reviewed its position in our Short Term Backlog, so that it is addressed sooner. If you have any additional information, different to what has been documented in the Description of this issue or previous comments, please do share it so that our developers can review this information when they come to investigate and resolve it.

Thanks for your patience

Makisa | Senior Product Manager, Confluence Server and Data Center

Don't waste your breath or time trying to get an update - Atlassian does not seem to care. As a workaround, you can return to the stone age of Confluence 5 and disable the collaborative editing. You can also stop paying maintenance I suppose

@qkunz @chuck Gee

did you tried to disable collaborative editing ? it seems a Common workaround for this issue.

@Stephen Kairys

Label affects-cloud is added on this Ticket (you can see this in the details section)

i think it will not helpful to ask any time the same question. if you affected then please vote as Affected customers in the people section on this ticket.

thanks

it also happens when we just open a document

Hi,

Does anyone know if this bug affects CONFLUENCE CLOUD?

Thanks.

This issue creates a major problem for our technical documentation processes and we need this problem fixed so the links work in a predictable manner as described in the Confluence documentation. We rely on the use of anchors and link to help with navigating long, complex parent pages, as well as many child pages. Without the links functioning as designed, and even worse, with the links behaving in an erratic manner, thousands of hours of work will have been ruined and we absolutely view this as a critical issue for ourselves and our customers. 

Please increase this issue to Critical.

The severity for this issue is Major or Critical for our us.  The inability to copy pages and retain our links makes the majority of our documentation in-useable.  We have 100+ page documents with 100's of links that can be randomly broken each time we copy the document to make a new revision.  Presently, there are no work arounds.  We are left with re-architecting our specifications to remove links or move them outside of Confluence which we do not want to do.

If this story is rated Minor there needs to be a workaround.  Could you please provide a work around or increase the severity to Major or Critical?

Not really expecting an answer, kind of getting used to a fact being ignored by Atlassian - but is there any update on this, please. When this will be fixed?

Hello,

Confluence Server 7.4.0 also affected by this issue.

Found workaround to fix broken pages.
In storage format normal anchor link looks like this:

<ac:link ac:anchor="contents">
 <ac:link-body>
   <strong>Table of Contents</strong>
 </ac:link-body>
</ac:link>

In broken page it's like this: 

<ac:link ac:anchor="contents">
 <ri:content-entity ri:content-id="DRAFT_ID"/>
 <ac:link-body>
   <strong>Table of Contents</strong>
 </ac:link-body>
</ac:link>

If remove <ri:content-entity ri:content-id="DRAFT_ID"/> with autoreplacement and save that page, everything seems to be working fine

Best regards,

Aleksandr Oliferuk

Is there any update on this, please. When this will be fixed ?

We have the same issue on our installation (7.3.5). Turning off collaborative editing fixes it.

Is there any update on this, please. When this will be fixed ?

Hello,

This bug affects the Cloud version too. Could you a label "affects-cloud" on this too please?

Thanks
Boris

Hi Team,

Can this issue be bumped to Priority = High? And worked on? We had to turn off collaborative editing because of it. In addition, we lost time repairing the broken links. And, for customers who still have it turned on, it's a problem waiting to happen

I also disagree with Symptom Severity = Minor.  Corrupted links are a significant issue, a lot more than just a mere inconvenience that can be worked around easily. 

Thanks.

Hey everyone,

We recently upgraded one of our Confluence instances from Server 6.4.2 to Server 6.7.0. It seems that this problem (corrupted links when I make an unrelated change) it happening rather frequently now. Including for two docs today, and these may be the only two I edited today.

On the other hand, t may not have happened much, if at all, prior to the upgrade.

Has anyone else noticed this pattern? I'm thinking the flashpoint may be the first time you change a doc after going to 6.7.0 from some (undefined) prior version.

TO ATLASSIAN: Whether or not the above is valid, it's obvious that the bug still exists under 6.7.0. Can this version be added to the Affects Versions field?

Thanks.

Hey, Ann,

To my knowledge, I've not seen the bug when COPYing a page. That said, since we do sometimes copy pages, I hope that this aspect of the bug can be fixed when the main issue (broken anchor links on current page) is addressed.

Thank you.

Hi skairys124192546,

No, there is not a separate bug for the same behavior during copies.

The bottom line is that if you want a bug report opened you may work with support through the support portal to replicate the issue.

Here is what I commented above on this bug:

aworley added a comment - 28/Aug/2017 11:40 AM
In the Community, links are also being reported as changing (as described in this ticket) when pages are copied with collaborative editing turned on: Copying page messes up links to anchors/headings

If you judge this to be an inadequate communication to the development team you may certainly work with support via the portal to get a new bug opened.

I replied on the Community post but did not update this ticket as the copy page issue was added in a comment directed at the Development team above. I cannot open a bug report based on experiences reported on the Community. A support engineer must reproduce the bug to eliminate environmental variables before a bug report can be opened. 

From our Bug Fixing Policy

Atlassian Support is eager and happy to help verify bugs—we take pride in it! Create an issue in our support system, providing as much information as you can about how to replicate the problem you're experiencing. We'll replicate the bug to verify, then lodge the report for you. We'll also try to construct workarounds if possible.

On the Community thread I explained that if you think the copy issue is a different root cause or want it opened as a separate bug report, the procedure is to create a support request:

Stephen Kairys Thursday
 
Thank you, Ann. Are you suggesting I open a new bug report for the COPY aspect of this issue? I have not seen evidence of it, but that does not mean there aren't corrupted pages out there I have yet to discover.

Ann Worley ATLASSIAN TEAM Thursday
 
I wasn't really suggesting that, rather letting you know that support requests are the avenue to opening bug reports. That said, if you are able to reproduce it I am sure the team would be interested, as these bugs with links are hard to replicate.

@Ann Worley - Has the issue described in the community forums: 

https://community.atlassian.com/t5/Confluence-questions/Copying-page-messes-up-links-to-anchors-headings/qaq-p/629893

been logged as a bug in your JIRA?

Thanks.

I am at my wit's end. This is yet another collaborative editing-related bug that's corrupted existing documents. A whole bunch of links broke in an important document and I have no idea how many other documents have been affected. Didn't you guys test these things before releasing? Once again, I've been spending way too much time chasing down document corruption instead of writing and editing documents. How can this bug have been reported almost a year ago and remain at status = OPEN?

ATLASSIAN: Please fix this bug ASAP as corruption is at risk for every day the bug exists.

ANYONE ELSE OUT THERE: The behavior I'm seeing when I click the link is as follows. It takes me into what looks like a page from the document page history, with the version displayed as Version 1. However, the content appears to be current. Have you observed this exact behavior?

Thanks.

Hello team,

it is also affected on 6.1.3.

Thanks you.