← All ideas
  • Published 9 Jul 2026

Batch Renaming needs some UX Love

I had a frustrated experience with Batch Renaming yesterday that I've end-up firing a bug report that turns out not to be a bug because the UX is not helping at all:

Issue 1: Batch Renaming is Context Sentive (even when 'ALL' is toggled) but it won't tell you that.

2026-07-09_10-20.jpeg

Currently it shows Types that if you select, it will silently fallback to some other Type that is accepted in the current context the operator was called. This already brings me to another potential issue:

Issue 2: Why the Outliner is not the "King" of the contexts for Batch Renaming?

Since it allow us to manage everything in terms of data-block naming manually, why still some Types are not accessible here?

And I wonder if the Context should really matter even when the user choose to perfrom on 'All'. I think being context sensitive in these cases just limits the usability of the operator too much.

The issue that brought me here: There is no way to Batch Rename Node Group Trees.

2026-07-09_10-44.jpeg

Currently the Type Nodes is meant to rename the name of the nodes themselves, which is hardly relevant. What we usually want to manage is the name of our node group trees instead so would be nice if we could do that. ( Just found another user reported this same issue )

Looking through other RGS posts related to Batch Renaming I top up others user requests

Include more relevant Types:

Other features

People mentioned this extension Simple Renaming which has worked for me on Node Tree Groups .

Thank you!

100%

Development Status: Open

Upvote 5 Downvote 0
cosmomidias
9 Jul 2026

0 Comments