DRAFT PROPOSAL
This is what site admins see in the UI:
This is what the people filling the form see:
I would like to propose the following changes: - Rename "categories" to "recipient groups" in the backend, since that is what people are actually creating. - Allow customizing the label of the "Category" field (what site visitors see in the form). Depending on the use case, you may want to call it "Reason for contacting us", or "Select department to contact", or whatever. - Whatever the label is configured to be, make that the heading of the "Category" column. - Potentially also allow customizing the label of each "category", so that the options shown to site visitors in the select can have different labels from what the admins call them "internally".
Recent comments
I read this quickly, so I'm sure I'm missing something. Check your active config folder. Fields have two components: Database tables Field info and field...
Field deleted, but: machine-readable name is in use?
BTW, this is still a problem in the D7 version (despite what that issue said), so I'm not sure this is possible. I'll have to look more closely into it.
How to order a view by its aggregated value
Hmm... I was able to reproduce this issue when I thought it would work. Wuold you mind opening an issue in the queue?
How to order a view by its aggregated value