Hey Folks - This is a +1 from my team, too.

Tickets are all-but-never 100% clean and sequential - there are assumptions that get wound and unwound, Scope Creep that must be handled, User Cases and Technical Information that must be aggregated and sifted once / twice / thrice - before the ticket expands-to-and-addresses the entire breadth of the issue raised within it.

For example... right now, I'm in the middle of aggregating all of a customer's disparate complaints (ZD, Email, Gong, etc) into one ZD thread, which I will then hatchet down sub-task by sub-task. I am just about to Slack my Customer Success Manager so that she can follow along: My Internal Note in which I aggregated all of their complaints is 5-7 questions down in the thread, already. I want to post a link in the Slack convo which auto-scrolls directly to this Internal Note, since it's the nexus of Current Understanding about this ticket, and will be for another ~12 ZD posts at least.

All that's required to produce this functionality is.... 1) The use or establishment link of some kind of link-safe unique ID for each Thread Tile, 2) A permalink button tastefully displayed in each a/o 2a) the Global Config therefore, and 3) the front-end functionality to Auto-Scroll to this thread post.

It would be great if this could get dispatched ASAP. I think this would be high-win for relatively low-effort.