Attach comments to board rather than object

➕1

We hit this as a real, live incident: routine board maintenance (deleting and recreating items via the REST API) silently destroyed several unresolved review comments a teammate had left via the UI, with zero warning. Confirmed via the API that a follow-up GET on the board's comments returned none of them - permanently gone, no recovery path.

Worth noting this compounds with another gap: comments have no independent DELETE endpoint either (405), the only ways to affect a comment via the API are PATCH resolved:true, or lose it entirely as a side effect of deleting its parent item. There's no "unbind" operation at all.

A few possible fixes, in order of preference:

1. Orphan the comment instead of destroying it (unbind it, keep the thread, fall back to canvas/unattached position).
2. At minimum, have the item DELETE response flag when attached comments existed, so automation can detect and warn before this happens.
3. Document this behavior in the DELETE endpoint reference - it isn't mentioned anywhere currently and is easy to trigger by accident.

​@Eca can we hope this enhancement proceeded?

Hi 

Thanks so much for taking the time to submit this Wish List idea. Our team will review this and it’s open for votes and comments. 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

Thank you again for helping make Miro better!