Skip to main content

When i move my design elements/frames/etc., I expect all the pinned comments to move with them – but they don’t. instead i’m left with a bunch of floating comments (that are not attached to anything), which requires me to manually re-read each comment and move it again to its correct place. this is frustrating and time consuming. but what’s worse is when another user forgets to move the comments after they move the design elements, so when i return to the Figma file it’s very difficult to decipher the floating comments because they are not pinned to anything so i have no idea what they’re referring to. please keep Comments pinned to design elements (so moving design elements automatically moves comments).

coming 2024,still out of this feature?


I found a workaround.


The comment seems to be attached to the most high level element on you canvas. This means, if you try to attach a comment to an element on an artboard… Figma will attach the comment to the artboard and not nested element. (hypothesis)


To make it simple,



  • if you can, set yourself and your elements outside any artboard.

  • Select the desired element

  • Create a comment

  • Move the element, the comment is now attached to it.


But I agree, not optimal at all.


haha…1 year later here i am…


Currently using sections with various huge component sets that have autolayout. When i shift position of the elements within the autolayout frame, the comments that i pinned on the nested frame don’t follow the element i shifted. We need to be able to pin to specific elements and not just top level frames, and need the comments to truly stay pinned. I am getting trust issues from this one.


Someone else has mentioned this here



That thread is marked as resolved but it really isn’t!


Also mentioned here as a bug



This is actually part of a bigger issue of how we relate to comments in general

which i stated here. It is not one or the other.


To everyone who wrote here, since this one was marked as solved and seems to not be sufficiently specific, i have made a new topic you can vote for: Keep comments pinned to specific nested elements (AUTOLAYOUT included)


Hey @Delia_Tomei_Villadsen, appreciate your feedback!

This is on our radar. I’m happy to pass this to our product team as a feature request for their consideration in future product updates, though I can’t guarantee an ETA for any improvements.


This is such an essential feature: I use auto-layout to organize rows of artboards and when I add a new one the comments stay in place while the artboards get shifted so it’s hard to see what comment relates to what. Allow me to anchor them to specific components in the designs so that they remain in place. Show a border when the comment is selected to easily identify what component it refers to.


This has been mentioned already in so many threads, can’t believe it’s still not been implemented: I use auto-layout to organize rows of artboards and when I add a new one the comments stay in place while the artboards get shifted so it’s hard to see what comment relates to what. Allow me to anchor them to specific components in the designs so that they remain in place. Show a border when the comment is selected to easily identify what component it refers to.


My team uses a lot pronouns in our comments. And our compositions use a lot of autoframing. I wish I could attach a comment to an object (photo, text, etc) so that when a section is deleted, and the whole page moves up, comments stick to what they are referring to.


we desperately need this @Figma_Moderation @support_team @Figma_Support @figma


pin/anchor a comment directly to elements within auto layout


or at the very least offer a click-drag that allows comments to be included in that selection so they move everything together.


FIGMA NEEDS TO BE A COLLABORTIVE TOOL - hundred of floating comments that are impossible to track and ensure feedback is being addressed is unacceptable


Hey @Sarah_Jackson1, thanks for the feedback!


As mentioned by Celine, our team is already working on this. We just don’t have an exact timeline we can provide just yet.


Also, please be aware that Figma’s Community support team does not own Figma_Moderation, Support_Team, or Figma_Support.


+1 I would also love for this feature to support moving frames to different pages, so the comments move with them.


I came here to ask the same thing, then I just noticed that comments can be reattached to certain elements but not others - it’s really finnicky. This needs to be fixed: to be able to drag the comment around and it should get stuck to the closest element, be it a frame / component / group / shape.


You can do that by right-clicking on a frame and selecting “Move to page” and a target page. Doing that will move any attached comments on the frame along with it.


Thanks @flauridsen I wish this also worked for cut & paste… that is what I always use to have more control over where on the page my cut & pasted elements land.


Another issue I face is, if I organise my files and want to move sections / artboards etc. to another file, the comments do not move with it. Even if I clone a file, the comments only exist in one file - so I have to screenshot the comments manually to keep them in the context.


wow, yes. need this.


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.


@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!


Reply