Why are we unable to create subcats for mods within the Staff category?

It is not the correct way to do it—but I did implement it in April. We don’t normally wait for bugs to get fixed or features to get implemented in order to get our stuff in order.

Yes, yes, and no. I spent many years as a software developer and manager, and I am well aware of what it takes to fix a bug. This fix would take a few minutes of development time, a few hours of testing time, and no more maintenance than the present version does now.

Your argument means that there is absolutely no point in developing anything new, then. There are thousands of teams using Discourse as it is—why spend even one more hour developing? Let’s use logic when we argue, please.

This was a uselessly rude assumption, which is obviously groundless given my comments above.

Actually, you are wrong. It worked differently, and better, for a long time. Here is an example of an existing, hosted Discourse system, that is 4-5 years old, with a native staff category that allows mod subcats:

The point has nothing to do with my system. I don’t need the change to make it work. The point is that every single Discourse system comes with a Staff category that is inferior in capabilities to what it could be, and what it was. If Discourse goes through the trouble of auto-creating a Staff category, why not engineer it well and cleanly? I am making a suggestion that is simple and easy to implement, and that will regain capabilities that are useful to those of us who deal with multiple categories of staff. The team is free to consider my suggestion—or not.