When is this bug backporting to the Enterprise versions of 7.4 and 6.13?
(or is it already, please? )

Thanks!
Rick

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

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

Hi,

It's happening also in 6.12.4, it's unbelievable that it's still not solved...

This bug is really messy. It blocks my teamwork due to template needings.

This is a kind of workaround but it is really akward:

Reference the anchor [ # anchorname ]. It creates a broken link but when you create the page using the template and saving the page it works.

This work around solved my trouble. 

Step1: Add a HTML macro. 

Step2: Add the below code in the HTML Section: 

<div><a onClick="window.scrollTo(0, 0);">Back to top</a></div>

This bug is really blocking my workflow too.

I have some images I'm using as links to pages and anchors..

I've read that the solution to get anchor links working is to copy and paste the link with the acnhor... but copy and pasting images in templates doesn't work due to either a bug or major design flaw: https://jira.atlassian.com/browse/CONFSERVER-45200

Is there a workaround for having images with links to anchors in templates?

Issue still available in confluence 6.15.2.

Welcome to 2019. Here, get some tea and cookies, it will take a while

Affect also Confluence 6.12.2.

Cannot believe this is still not solved (2012)..

Michael

It is essential that this bug is fixed for the type of documentation that we create.

I'm glad it's actually in progress, but would like to know if we can expect an update soon - by the looks of it the bug was reported six years ago...

So the solution to this is to not provide this in the template and have it in the page... That is not a solution at all!

We need the template to provide a standardized format to ensure everyone follows a simple flow to generate our project information. It isn't simple to say create the template, and then edit the page with all of the anchors manually each time a new page is created from the template. That is wasted effort when the system should allow us to provide the standardized component directly within the template. 

This is our ticket number if necessary: JST-412736

Has this been resolved. I am still running into this issue in August 2018. Can someone tell me what is the resolution. Need help ASAP. Your help is appreciated! 

hallo

Dear a.murdoch , I agree that this seems like a trivial bug to fix ; however, there is indeed a bigger picture you are not seeing .

I am all for applying quick fixes when they make sense ; however, in this particular case a more robust solution is preferred which as it turns out requires lots of untangling.

Thank you for your patience

I'd love to see an update on this! A fix would be greatly appreciated.

Although I resist making judgement on how easy a bugfix would be without seeing the big picture, in this case it does appear to be purely a validation error in the editor. Manually entering links to anchors in templates via Markup seems to work fine in every use case I've come across (including Live Templates using the Scaffolding plugin). It does appear the editor is simply seeing links to anchors as invalid and so should be a relatively simple fix.

Not just in templates. On a normal page I cannot create a link to the official Jira Service Desk REST API, such as: https://docs.atlassian.com/jira-servicedesk/REST/3.10.0/#servicedeskapi/servicedesk/\

/requesttype/{requestTypeId}/field

Edit: just pasting the link with ctrl-V works, and then I can also edit the link's label. Pasting the link as the link address fails with the usual error message, though.

We would love to see a fix for this, since we're working a lot with templates and like to use anchors within the documents!

Does Atlassian not have a process for updating their users?

This has been open since before my kindergartner was born. This is a company that specializes in processes? @shaffenden

Still existing issue

Also in Confluence Cloud! Please rectify this ASAP

This is also an issue in Confluence 6.1.3

I found a situation where the workaround doesn't work: if I want to place a link on an image. I can paste in an image with a link and everything looks fine; however, after saving the template and reopening it, the link is gone.

The workaround works only if you do [Lind description|<linkName>] in your template and not if you insert a link from the menu. (thought people would be interested to know this detail)

For RL and Jon: You made comments about SharePoint doing much better. Can you elaborate on this? As far as I've seen, the SharePoint wiki features aren't very good. We just upgraded to the latest Office 365 SharePoint and I played around with the wiki features and it doesn't seem like much has improved. It still seems far easier for me to create content quickly in Confluence. Now if I want to store Microsoft Office documents, SharePoint handles that better than Confluence. There are a bunch of other features in SharePoint, including wiki, but Microsoft has mostly ignored them, so much that they don't really seem that usable. I'm curious what you're finding in SharePoint. Maybe I'm missing something?

This is disappointing to see this bug had been open for 4 years...  For those not aware there is a workaround, it looks ugly when updating the template but works otherwise. Thank you to the person who posted the link to this open bug.  https://answers.atlassian.com/questions/269807/cannot-seem-to-create-a-template-with-anchors-and-internal-page-links-link

Thats pretty awful when sharepoint can do anything...Wow Atlassian fix this now I do not want to go to sharepoint.

Since it is unassigned, i don't think any of the Atlassian support ever watches or gets notified for this issue. I did already but no use.

Atlassian do not create templates so this is only an edge case for them.  And for all others go for other products. MS Sharepoint is doing far better than this.

I am about to ask all 200 of the users in our instance vote and watch this item, would anyone else that would like this fixed consider doing the same?

Possibly if we can get all current 84 watchers to comment on this post it will get some increased visibility. I too am concerned this issue has been flagged as "edge case" as it obviously impacts all cloud users and there is no viable workaround. Please consider fixing this issue Atlassian!

I voted for this ticket the first time about 2 years ago. We still need this features: please prioritize this.

Us: "Guys, I've been on hold for five years now. Any updates? It seems like being able to link from one part of a template to another part of a template is a pretty basic essential part of what a template feature is for."

Them: "Nope, this is an edge case. Please continue holding and pretending we give a damn."

Them: "Hey guys, we've built you this awesome feature that lets you pre-build pages so you don't have to start from scratch every time"

Us: "Oh great, so you mean I can enter text and stuff?"

Them: "Yes you can!"

Us: "Awesome! So I can link from one part of the text to another part?"

Them: "...Uh. Please hold. Your expected wait time is approximately: five years."

This bug should be high priority. Not been able to create templates with anchor links defeats the purpose of using templates...

We use anchors pretty exclusively for "return to top" or "jump to this section of the page" type deals. It would be very nice if this was possible to recreate in templates. 

Agreed here: This has affected the way I need to make my templates and we are heavy users of templates in the consulting world. When designing templates we must constantly work-around this issue.

I see this was just classified as "10% - edge case or very hard to experience." I disagree. I can see that it may be prioritized as low because there's a workaround, but it's pretty easy to experience the problem. It seems pretty fundamental to me, not an edge case.

+1 Quite annoying and getting old. A fix would highly be appreciated.

"Feedback from the consumers is that it off-putting/disconcerting..." = understood and definitely concur.  Let's see a fix, please, Atlassian.

Workaround does work. Feedback from the consumers is that it off-putting/disconcerting i.e. folks who are using the templates that we create for them to do their work do not like seeing disconcerting messages spread over a page, and takes their focus of them do their job by just focusing on the content.

All please try the workaround... create a page containing the layout, formatting, and anchors you need for the template.  After saving the page, enter edit mode.  Copy/paste all content into a template you are creating.  Save the template.

The template will show "Broken Link" notices (where the anchor links are placed) if you go back to edit it.  A new page created in Confluence using the template will also show "Broken Link" notices before initially saving the page.

HOWEVER - once you save the page, the links and anchors will all be in place and working.

It is definitely a frustrating issue.  Still experiencing it here, as well.  Yes, it is an irritation.  But, the workaround is good and only a slight alteration of process to deal with (create Confluence page first, copy to template).  It's not a showstopper leaving you dead in the water!

Just came across this while creating templates. Quite frustrating.

+1

I don't understand why the issue is being downgraded. I work at a large company and not having this functionality could be a showstopper for using confluence. Anchoring tags to specific sections of a confluence template is highly important to us.

We have an on-premise installation and are affected by this issue; however, the workaround does work for us. Still, this bug has been identified for almost 4 years now and hasn't been fixed? I keep running into many Confluence bugs that have been reported years ago and never fixed. That's not encouraging.

This is not an issue with an on-prem installation. Is this a limitation by the team, similar to restricting users the ability to edit HTML directly?

Echoing the comment from @Jacob-Jan van der Spek, asking users to add this to EVERY page, EVERY time is too technical. We need a method for including this in the template.

2nd the previous remarks: we want to use the link to an anchor in a page for a bit of multi-language support. Manually adding the links after creating the pages (by multiple employees of our company) is too technical, so a solution within the template (where it should be), should be available.

Same here. Seems that neither the anchor link functionality nor the workaround work correctly. Very frustrating as it should be fairly basic functionality.

Using version 5.9.10.

Same issue also with one of the latest versions 5.8.18 and 5.9.10.

Very annoying to see that this hasn't been fixed for such a long time

See Karl Perry's 2014/03/07 Atlassian Answers comment at the following link for steps to recreate, screenshots, and workaround success description:
https://answers.atlassian.com/questions/269807/cannot-seem-to-create-a-template-with-anchors-and-internal-page-links-link

This issue is definitely still happening. Tried to update a template with a few anchors (anchors get created just fine), but when linking text on the page to the anchor "The markup provided is not valid link markup" message appears and the 'Insert' button remains greyed-out, preventing save.

Also discovered the workaround noted here - it is good... copied the anchor-linked text sections from an existing/saved page and pasted/inserted into the template. When you create a new page from the template and save it, the links and anchors work.

JUST A HEADS-UP for other users - when creating the new page from the template (prior to saving it), you will probably see a red-warning box with a "Broken Link" notice where the anchor links sit on the page. However, when the page is finally saved, the text/links and anchors work. Also, after saving the page and go back in to edit, the warning is gone.

I stumbled over this problem. An early solution would be helpful.

@Steve Haffenden, any update on this? Does it have a target date? This was filed in 2012. I think people deserve an answer, if not actual responsiveness to the issue from Atlassian.

This is a serious issue for my team also, we've tried the suggested workaround but on attempting to open these appear as broken links.. Please resolve

Also found this to be an issue. Will this be fixed soon?