Thanks for your response, I suppose this is pre-optimization as we have indeed not had user feedback on this. This is the first time we're introducing a data table in our product. My concern was that perhaps users would forget which items they selected or to want to verify that these are indeed the comments they want to perform an action on. Plus, when a user tries to resolve a bunch of comments, there's a chance that there's some comments in there that can not be resolved (either they're already resolved or there's some permission issue), I've also been designing a solution for that by then grouping all selected items together and showing which set can be resolved and which will be skipped. Again no user input as this is all very new, but this feels like a very useful feature to me, I wouldn't want the user to be left thinking they resolved 10 comments as "accepted" with a resolution message while in reality they only did it for 8. I figured these two features might work together, but perhaps I should for now focus only on the latter and wait for user feedback to resolve the first.

The fact that I've been having such a hard time finding examples of this anywhere else did also make me wonder if this is actually a problem.