Revert the change that requires Ticket Status to be a column in all views.

Hi Zendesk Product team,

I just finished working with support (Ticket #12896498) in which I was told that a recent UI/UX change we're seeing is intentional. I was advised to share feedback about this change here, so here you go!

What changed?

This change requires any ticket view to have a mandatory Ticket Status column. It cannot be removed, only the position adjusted. Not only does it appear this change wasn't announced (?!) it's hugely regressive to administering the system and demonstrates a lack of awareness as to how your customers use your platform.

What's the impact? Why is this is an issue?
We create views for different tickets with the status filtering put into place in the view parameters itself (ex: Status = New). This means that anyone viewing the tickets there can safely assume the status is New and it's not necessary to include a column for it.

The impact is that we cannot display as much data as we used to, because we are forced to devote a column to data that is not needed in our structures. Additionally, we use Lovely Views (as do many of your customers) to manage our views properly. Lovely Views displays status on its own, without forcing us to take up one of the 10 precious columns we have available for data.

The Ask

1. Revert this ASAP please. Please don't assume which data should be shown about tickets on our behalf. That's very organization and configuration dependent.
2. Log all changes in your release notes.
    

Below is what a Lovely Views user would see.