Keep Comments pinned to design elements (including nested)

Confirming this is still a, very frustrating, issue.

@dvaliao Thanks for your update.

I have one question and one input re: comments and pinning to design elements:

1. Is there a link where we can see roadmap (i.e.: now/under development (i.e.: coming out in the next update), planned/next (after this dev cycle), later)?

2. Comments are so underdeveloped in Figma, I could write an entire PRD just about comments for Figma (which is sad for many reasons). Here’s one I desperately need:

As a designer, product manager & developer, I want to view an older version of a frame to identify what comments resulted in what change. This serves a purpose for new designers/product manager to understand why the design is in the stage it is at right now, and not suggest changes that were deprecated. For developers, I think it is obvious.

I realize the workaround is version history, but that is a global view, not a frame view. Also, when completing development, it does not restore comment history nor can I do a side by side comparison and have to rely on my memory switching back & forth.

Hey @_Dema_Design_Team, you’re welcome!

While I wish I had a better answer for you, right now, we don’t currently have a public roadmap for coming features. But this is something that my team here in the community have been trying to advocate for - stay tuned!

In the meantime, keep an eye on our future releases here. If there are any updates from our collaboration team about this specific feature request, we’ll be sure to provide an update here.

Adding to the pile. It is incredibly frustrating that the comments don’t move. I have to spend a lot of time copying designs to new pages and then doing this weird “taking feedback notes” task in order to keep the original comments “attached” to design elements.

I usually work from a draft Figma file then when my spec is completed I move it over to a main file so that theres nothing in there that devs cant build. When I move my designs I’d love if the comments would move with it to reduce having to type them again.

I know we have the ready for dev feature but I just like my main file to be cleaner and smaller in file size so it loads faster. Therefore I dont put my draft work in there.

Thanks!

+1.

This can do so much for collaboration.

Same issue as everyone else. Dear Figma,… it’s been 3 years since this thread started. Can you prioritize this please?

same here. and to add another use case: i just wanted to move a huge discovery page to another file, since along the way it was clear that the asset would belong to a different product in our ecosystem of services. now i can either move AND loose all 40+ open comments or keep the page in the “wrong” file. frustrating. if only “move page to file” was possible. just like “move to page” is possible for layers.

+1 to bump and boost—Figma team, please prioritize this extremely frustrating basic UX issue over AI integrations.

I can’t believe this is still an issue! Comments should be pinned to elements, even if those elements are within a group/auto layout/etc. Now, if my client leaves a few comments on top of specific elements, then I add some text to an element at the top of the page that pushes the content down the whole page, all the comments below are no longer pointing to the correct elements because they didn’t flow with the content. So frustrating!