Why has this issue been marked as “solved” after post #13? Comments following top-level elements are only half of the job, as proofed by all those comments above. Please correct the status of this idea, @Figma_Moderation, so that product owners can see it and take it into account.
Hey @Dominik11, thanks for flagging this!
We’ve removed the suggested solution and passed this onto our team to look into.
Btw, we do not own Figma_Support or Figma_Moderation, so there’s no need to tag them in the future.
Happy to hear this, and thanks for your clarifying 
Confirming this is still a, very frustrating, issue.
2 Likes
@dvaliao Thanks for your update.
I have one question and one input re: comments and pinning to design elements:
-
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)?
-
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.
1 Like
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.
1 Like
Same issue as everyone else. Dear Figma,… it’s been 3 years since this thread started. Can you prioritize this please?
2 Likes
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.
2 Likes
+1 to bump and boost—Figma team, please prioritize this extremely frustrating basic UX issue over AI integrations.
4 Likes
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!
2 Likes
Hey All, so sorry for the continued trouble!
The team confirmed that the underlying issue is that Figma can only pin comments at a set of coordinates on a top-level frame, not any of the nested elements. This means that resizing the frame or rearranging the elements inside the frame can cause the pins to lose a clear reference to the nested layers that they were previously shown.
We’re trying to build a better function that allows comments to pin to nested elements, but until then, please keep this in mind when trying to move your designs with comments in the future!
I would like to have a feature to move comments between pages. As recently I moved some of my design to some other pages in the same file, the comments (there are mostly a hundred) were not moved along.
It is pointless if we read a comment pointing on nowhere.
3 Likes
you should have your whole company drop everything else and work on this exclusively. The commenting feature is useless otherwise
Hey @David_Platt1,
I understand your frustration. While I wish I had that type of authority, the teams ultimately chose their priorities, so there’s no specific timeline to share on a fix.
To be transparent, the main issue the team is trying to prevent is when a user deletes a high top level node that contains lots of comments, the number of API requests fired all at once could be substantial, causing much bigger performance issues.
Rest-assured that our collaboration team wants to fix this and continues to revisit to try new approaches, but until we have an optimal approach with more safety guardrails for issuing lots of comment API updates all at once, it’s best to comment on your top level frames to ensure your comments stay pinned when moving your designs.
Comments are selectable items in the canvas. Therefore when they are part of a mixed selection set they should obey basic canvas inputs, like moving or deleting.
I hope this inconsistency gets resolved soon. It’s causing a lot of manual work when cleaning up a component file.
2 Likes
+1 to prioritize this. I might be using 5% of the whole set of Figma features, but this is a time-wasting activity.
Still really wishing for this feature. I put a lot of comments within my top-level Autolayout frames and every time something in my design changes place, I have to move the comments along with it. It’s soooo time-consuming and frustrating.
I’m continuously surprised that this hasn’t been fixed yet because Figma is normally so good at improving/updating the things that really matter!
Edit: and indeed also being able to cut/paste to other pages/files without losing comments… I often build stuff in a ‘sandbox’ type file and then have to re-add all my comments if I want to move it to a project file.