# Testing Nested Replies on Meta

**URL:** https://meta.discourse.org/t/testing-nested-replies-on-meta/398759
**Category:** Nested Replies Testing
**Created:** [March 18, 2026, 8:56pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759 "2026-03-18T20:56:48Z")
**Posts on this page:** 1
**Showing post:** 91

<div class="post-metadata">

### Author: ![markvanlan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/markvanlan/32/160087_2.png) [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [April 21, 2026, 1:12pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/91 "2026-04-21T13:12:24Z")

</div>

It’s not missing the “Parent post” I don’t think.. when you’re deeplinked to a post it shows the parent as well. I believe the issue is mainly the consolidation of “replied” notifications. They get lumped together as `N new replies` and only link to the lastest reply, so the `N-1` are super hard to find. Really need to think of a solution there. I’d love to _not_ mess with our notification system.

Maybe we could append a query param to notification URLs for nested view and have a “step through” system for watched topics or something. cc @Lilly

---

_[View the full topic](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759)._
