cmarriott any update on this? Would be a nice feature to have...

I was just trying to get our new program manager to adopt using Confluence over her preference for Microsoft SharePoint for our project documentation/collaboration model. It's a pain for her and others who don't LIVE in Confluence – that in order to respond to an @mention notification email from Confluence they have to log in and go directly to the thread and respond there. They are used to responding to a Jira @mention email and it gets added to the Jira issue's comment thread, so why not expect the same to work for Confluence??? By the way, it has been 14 years since the original Jira ticket on this problem was created – and that's 13.9 years longer than we should have to wait.

This functionality seems pretty basic and is supported by other tools. Folks on our team expect such capabilities with a tool as sophisticated as Confluence, and are disappointed + surprised at how much they actually use this with other tools. Please re-prioritize this.

michelle.vincent the best thing to do would be to raise a support request at support.atlassian.com. They should be able to help you diagnose the issue and raise a bug with the development team if required.

We are seeing an issue currently in Confluence Server 7.4.6. The notification of a comment includes several links. If you click the title link in the notification, it gives you a focused comment link. When you click this link, if you try to reply, it just spins and never brings up the comment box. If you click the reply link, it takes you to the reply to comment link. This one does work for us.

Is this intended behaviour that the focused comment link will not allow you to reply? If I click that link, I have to remove the extra portion of the url, refresh the page, and then it allows me to reply to the comment.

Another 8 years have gone by with no movement on this failure. Priorities, Priorities. I'll see everybody again in 2029.
 

Hi All, 

This issue has been deprioritised as our teams shift focus to ensure that Confluence can scale to meet the needs of our ever-growing customer size. We still have this suggestion on our backlog and would love to get back to working on it but we, unfortunately, don't have an ETA at the moment.

Regards,

Matthew

PM Confluence Server/DC

I would like to know as well.   I notice that Mathew is no longer assigned to the issue.

Dear Matthew,

what is the current status of that feature implementation?

Best regards

André