Anchor macros randomly break.

Hi. We're in the process of inserting anchors within our documentation and we're finding that the anchors are randomly breaking and renamed.

For example, we create an achor called Requirements

Later, when testing, we find that links to that anchor have been renamed to Requi. We fixed it, and later we found it called Requ.


Of course, any link within the document that links to #Requirements is now broken.

Any ideas?

Edit: Update with clarification:

The anchor names remain the same. It's the links that get renamed.

For example, I might have text that says "check the requirements section" and the link is to #requirements.

Later I check and the text is the same, but the link is now #requi and doesn't jump to the anchor.

5 answers

This widget could not be displayed.

Matthew, I'm sorry I wasn't clear.

The anchor names remain the same. It's the links that get renamed.

For example, I might have text that says "check the requirements section" and the link is to #requirements.

Later I check and the text is the same, but the link is now #requi and doesn't jump to the anchor.

This widget could not be displayed.

When you say it has been renamed, do you mean the actual <a> (anchor) tag within the page has been "renamed" or the text in the link to that anchor tag has been "renamed".

This widget could not be displayed.

Huh, I use a lot of local anchors and haven't seen this before. I can't think of why it might be happening. Can you reproduce this, or is it fairly random? I'd say if it's reproducible, you should file a bug. If not, hopefully, someone else can chime in and suggest what might be happening.

This widget could not be displayed.

It's fairly random. Me (and my documentation team) just noticed it this morning. I haven't found a way to reliably reproduce it.

Our workflow right now is focused on adding links, anchors, and cross-referencing articles. So we're going through articles and adding this, then we check each others' work. We fixed links, but now we're finding links that we /know/ we fixed broken again.

This widget could not be displayed.

I guess one thing I would do to diagnose would be to look at the history of the page and diff the page with the previous to see when the change occurs. Not sure if this is going to lead to anything, but at least there's a chance that a pattern will emerge.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published Tuesday in Confluence

Add-on evaluation with confluence templates

Atlassian market place contains number of Apps/Addons which improves the capability of out of the box Atlassian products. It is good to follow a plugin evaluation process before install add-ons. So t...

96 views 12 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you