Hi, yes this is a legitimate issue. The problem is that regions are associated with locations, and that data isn’t readily available in the admin view. It used to be that we also maintained a hidden custom field on the meeting for just this purpose, but took it out to streamline the database footprint for very large areas with lots of data, and also because having duplicate data was causing some integrity problems.
There is probably a way to have the best of both worlds: no extra data while also bringing back the regions column in the admin view. I would love it if a programmer could take a look and submit a pull request. There is a Github repository here: https://github.com/meeting-guide/12-step-meeting-list
