Ability to archive (not delete) custom fields
Kasper Dam
Companies evolve over time, and so do workspaces.
This means that custom fields can become less or more relevant over time.
Similar to how we can archive tasks, I'd love to see the option to archive (but not delete!) a custom field.
This would benefit companies with:
* A lot of historical information. Who wants to store their information in one place (but not delete!)
* A lot of experiments and want to store the results but avoid cluttering their fields simultaneously.
* A fast-moving nature that evolves over time, and as a result, would like to archive a custom fields to keep things neat and tight.
Photo Viewer
View photos in a modal
Log In
Destiny Pidgeon
100%. I should be able to archive the field so that it doesn't show as an option on new tasks in that area, but the data still populates (and I can also still filter) for tasks where data had been set for this field.
I'd also request the ability to archive options in fields with similar functionality. The option will no longer show for new tasks/form submissions, but it will remain set to the archived choice on pre-existing tasks.
Clemence Wiart
Also, archiving lists/folders/spaces should automatically archive the custom fields that exist ONLY in those areas. The Custom Field manager should have an "archived" section just for that.
Caroline Ginty
Merged in a post:
Archive Function for Custom Fields
Kat Forster
Ideally, our team would be able to archive custom fields that are used to track items like events and company initiatives (etc.) that occur annually. We currently have so many fields takings up visual space (read: CLUTTER) in our account, yet we cannot delete them because that data is connected to past work for which we would like to maintain accurate records. It is overwhelming for current and new team members to be expected to utilize custom fields when there are so many to choose from, and many are outdated fields at this point but they cannot be deleted!
J
Joseph Plaizier
This would be wonderful! We have a lot of historical data that we want to retain, but also want to clean up our workspace so that we don't have custom fields in locations that they are no longer needed with update workflows.
Rosalia Adisti
yes please, I don't want to lose historical data but want to clean up our workspace!
Sarah Wyatt
Adding a comment in support of this request too - want to try and rationalise our custom fields, but not lose historical data
Lilly
This would be SO nice. I have a lot of fields I have held off on removing because I wanted to be able to preserve historical custom field data, but it creates clutter in the workspace.
Elizabeth Bazan
Yes, as our processes change, we have some fields that are no longer needed, but I don't want to have that information just missing from our completed or archived projects.
S
Sarah Wise
This is so so needed! My custom field manager is clogged up by many "INACTIVE" fields. I wish there was an easy way to mark fields "Inactive" but still allow them to show up in any reporting.
S
Sumkey Hoo
Sometimes we might just want to remove a custom field from view, rather than delete it. +1
Natalie Williams
Sumkey Hoo agreed. This could be a workaround (admittedly not ideal) for being able to downgrade a cf from a higher level in the hierarchy. I've got a CF that was added at the workspace level when creating a calendar view. No warning prompt so it was added to the whole workspace when it only belongs on a handful of lists. And there is no way to downgrade a cf from the workspace level without creating a new field, manually populating the info, and then deleting the incorrect field. That would take days, such a waste, that (a) could have been avoided with a warning prompt and (b) should be able to be corrected with the cf manager.
Load More
→