3

To reproduce:

  1. Go to the Site Configuration, Database tab
  2. Enable one of the custom fields and give it a name so you can recognize it
  3. Save the options and then go to the List view
  4. Use the column picker menu on the right to include the custom field in the list
  5. Go back to the configuration for the custom field and disable it
  6. Go back to list view

Notice that:

  1. The column is still in the list
  2. The column is no longer in the column picker, so you can't remove it
  3. The column is not on the Customize Filter page, so you can't remove it

Only way to remove it is to temporarily enable the field, and then remove it, before disabling it again.

My question:

  • Can someone at Fogcreek verify that this is indeed a bug and thus register it, or tell me where I went wrong? :)

Fog Creek Case FC1961155

flag

1 Answer

1

This is definitely a bug (albeit one that is pretty easy to workaround). I've filed a case and we'll get this fixed ASAP. Thanks for the exceptionally well detailed repro!

(Note: this isn't an issue for fields added via the Custom Fields plugin; only the built-in custom fields exhibit the problem.)

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.