The qa_expand_key query parameter does not work as it used to, at least while the developers are working on some new API changes. As such, the qa_expand_key query parameter, and related queries are not supported at the moment. So when a user clicks on a notification, it doesn't bring them to the particular section that the comment is in (as it did before). Bear in mind, this is with limited knowledge of the agenda of the developers, meaning they may have removed the query functionality intentionally.

To the second part of what you said: I have to agree that this would be great in terms of efficiency! There have been many times when I open a help request with like 5 or 6 long help requests, and I have to find the correct one. While not impossible, it would save a lot of time!

As you may have experienced, there are a few changes happening so I figured someone is currently working on the code.  I thought I would get that Recent suggestion in while they are still making modifications.  I hope they read your post (a second opinion).  Thanks!