# Introducing nested replies **URL:** \ **Category:** Announcements\ **Tags:** nested-replies\ **Created:** [May 12, 2026, 11:21pm UTC](https://meta.discourse.org/t/introducing-nested-replies/402812 "2026-05-12T23:21:22Z")\ **Posts on this page:** 1\ **Showing post:** 16
**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:** [May 13, 2026, 7:47pm UTC](https://meta.discourse.org/t/introducing-nested-replies/402812/16 "2026-05-13T19:47:16Z")
> [@Richie](#): > > Does this suggest it should be tested in our communities in isolation first, before we all pull the trigger and convert every existing topic? ๐Ÿค” If it were my community I would test in isolation first. On the other hand we would get more valueable feedback faster by you enabling for your whole community ๐Ÿ˜‰ . Jokes aside, I do think testing in isolation is probably smart but there is no destructive data migrations here. It can be enabled and disabled safely. No decision you make here will lock you in either direction. > [@Richie](#): > > But itโ€™d need to be made very clear that there is no coming back from this ๐Ÿ˜… I guess I sorta accidently answered this part! Enabling nesting simply creates a `nested_topic` record for each topic in the DB and kicks off a job to calculate reply counts down the ancestry tree. Disabling nesting removes that `nested_topic` record and youโ€™re back to flat, no issue. > [@Richie](#): > > Will this feature be implemented here on meta first, or on [https://try.discourse.org](https://try.discourse.org) so we can test it outside of our production environments? Feel free to play with it in this category: > **[Nested Replies Testing](https://meta.discourse.org/c/nested-replies-testing/213)** > > Category used to test the very experimental plugin https://github.com/discourse/discourse-nested-replies/ --- _[View the full topic](https://meta.discourse.org/t/introducing-nested-replies/402812)._