Keep Comments pinned to design elements (including nested)

@MayaShendelman I have the same problem, but in Figjam. And it’s a huge problem. I am mapping flows in our app with screenshots (photos) and I need to attach a lot of comments to these screenshots, which I should rearrange all the time, but because of this problem, I can’t.
In here: https://help.figma.com/hc/en-us/articles/1500004290941-Comments-in-FigJam#Add_a_comment I was reading that the comments should be normally attached to an object or a sticker ( I imagine my screenshots are counted as objects?) but I see in their video demonstration that the object should first get a blue outline to look selected, and then the comment should attach to it. But I don’t see any blue outline on the objects I hover over when in comment mode.
As I mentioned before, it’s a vital thing for my work to be able to attach these comments, and I would love at least to have another way to comment if this doesn’t get fixed.

Exactly the same issue. Would be great if we can choose to have floating comments (as they are now) or pinned comments (put on top of a frame e.g.).

Now, we can’t move anything anymore on the screens, because we would break all the comments. Makes the whole comments thing a gamble to use.

Yes!! Imo comments should always be pinned to an element. A frame or group at minimum - it might be cool for them to attach to specific layers, though.

Miro’s implementation of this is good. Comments pin to specific entities and move with them.

Upvoting this one. Agree with above comment about Miro—I was disappointed Figma’s commenting doesn’t work like that. Roughing out our wireframes takes a lot of collaboration and I’m constantly moving frames around … so this commenting function is a big pain point.

Repro steps:

1. Add a comment to a prototype
2. Close the window, and reopen
3. Try to find the comment and notice that it is not anchored to where you added it

Comments should move along with the frames when you move them, and with elements in general

I would not enforce this as a standard, but rather as a option. Sticky comments vs normal comments. I don’t see a need for permasticky. But I do agree that it would be helpful in some instances.

Comments connected to a specific element in a frame would be great. I have the same issue - when the design above the comment changes, the comment becomes disassociated and it’s very hard to figure out what that comment relates to.

Found a solution to this. When you want to pin a comment to an individual screen, please make sure that it’s not inside an auto-layout. Remove it and make sure that it’s standing individually, that way, the comment will ever be moving with that screen/wireframe.

When moving frames around in Figma or across different pages, the comments do not stay attached. This is extremely frustrating to those designers who constantly reorganize their Figma by different development phases. The comments are super insightful in communicating with our dev team across seas and need to stay attached to the frames.

The comments should now be pinned to all top-level elements:

video source

Continuing the discussion from Keep Comments pinned to design elements (so moving design elements automatically moves comments):

I was working with this fix and I’ve noticed that the comments are not sticking to individual elements if they are in a frame. For example, if I have a desktop web page layout and I want to comment on a specific section, and then I reorder the page sections, the comment will not move with the element, but stay pinned to the original location within the overall frame.

@Gleb please see above

+1 to Kyle_Holten’s video. I’ve been similarly running into this when trying to attach comments to child frames that need to move around within the parent frame (e.g. table rows).

+1 to Kyle_Holten’s video.

I have made comments throughout my file. Later down the road I have done some re-organizing where I have moved a screen to a different page or even just moving it to another spot on the screen. When I do this any comments I have made pointing out feature functionality stay in place and I have to manually move it to the part it should be attached to. It would be great if we could pin a comment to a frame or element so that as it moves the comment follows.

I don’t think this is fixed. The comment may stick to a top-most frame, but it doesn’t respond to things within the frame, so if you’re making a comment on the contents of the frame and things get adjusted, it doesn’t move with the specific content being commented on (e.g. If you make a note about a field in a form, then other fields get deleted so the original one moves up, the comment doesn’t go with it)

+1 on comments in framed elements: a shortcut like CMD + C on a Mac to enter a comment and pin it on a framed element would be a great fix!

Ok, haven’t read the whole thread here… But I just learned that if you use the “Move to page” function, the comments are following when you move it to another page. So mark, right click and choose page to move to.

This is still an issue… Comments stay pinned now, unless you move something to another page, then the comment gets left behind.

Looks like Jessi above has a work around, but would be better usability if it just stayed with element, and we didn’t have to use right click menu.

In a FigJam I noticed the comment state highlights objects as you hover over them, and I wondered if that meant your comment would get stuck to that object.

I imagine this could serve lots of potential purposes, but the first practical one is that when objects get moved around, the comment pointers could stay pointing at the original thing.

Other extended ideas:

• When the object is deleted, the thread is resolved by default.
• When the object changes, that could be reflected somehow in the thread, so the discussion evolves.
• Discussion can now be tied to all kinds of text, styling, etc…go wild on your analytics/insights…but what is useful?!

Mostly for starters I want comment locations to stay relevant in the flow of working.

Hi James,

I think that the object/comment used to be like your describe it: when moving the object the comment would stay on the same canvas-position.

But I just checked right now: windows Figma app 112.2: now when I move the object, the comments follow, both Design/FigJam. Was this just fixed maybe?
😕

Up voting this one. Still a big issue for me!

Same here. Would love to have an option to pin comments to elements - suggestion, if deleting the element it would be nice to either:

a. Keep the comment per default but make it floating with a note saying something like “pinned element deleted”
b. Get a dialogue with the option to either keep the comment (floating) or delete it

Did this get resolved? I am still experiencing this and is so time consuming.