Archive Custom Field options (Labels, Dropdowns)
D
Deb Dharmaraj
Would be great if you could archive custom field options so that if using it for job numbers the drop down doesnt keep getting bigger when you are 6 months down the track. Yet you dont want to remove them in case of looking back or reporting etc.
Log In
Caroline Ginty
Merged in a post:
Ability to set custom field dropdown values as "inactive"
S
Shelby
I use dropdown values in custom fields for planning sprints. The problem: Over time, the number of presets I've created is only going to increase, and wading through the drop-down menu is becoming cumbersome. I don't want to outright delete existing options, since I want those values to remain available for reporting purposes. But: I want the option of only seeing "active" values when managing tasks and assigning them to sprints.
What I think I would like is the ability to (1) set custom field dropdown values as active/inactive; (2) have "active" values appear by default in changing custom fields in the list or when editing an open task. For me, having active values be the default visibility for creating filters as well would be good (with clickable option to see all?) but that might be a separate feature request and isn't my main priority.
M
Midnight Sunday
Surprised this isn't something implemented sooner!
In our use case, we have old clients that are no longer with us but still are in Accounts (labels) custom field. So in our list of choices when applying a label to a task or filling out a request form, these old clients still populate.
M
Miriam Daub
Ideally this could be prioritized - we end up having to create new fields so that the values are up to date, which is very cumbersome to maintain and is a poor design structure.
Caroline Ginty
Merged in a post:
Retire picklist values without losing historical data
Katie Desjardin
I would like a way to mark a picklist value inactive rather than deleting it in order to retain historical data. For example, if I have a custom field with 4 picklist values (Orange, Green, Yellow and Blue). These values have been used for years and today we find out we no longer need “Yellow” as a choice. We want to prevent users from selecting it in the future, but we don’t want to lose the value on the tasks it was previously used on in the historical tasks – just prevent it from being used moving forward.
Caroline Ginty
Merged in a post:
Deactivate Old Picklist Values
Danielle Little
Currently, you cannot deactivate any values and instead, you are forced to delete the values or create a duplicated field to remove it. This is not helpful because we want the ability to see what happened with a request previously while also being able to keep our values updated so old values are not being selected. This is not helpful from a reporting perspective either.
Katie Desjardin
Justine Dechaine
Would love to bump this up! Our fields are changing as our company changes. I want to remove a drop-down option, so no one uses it anymore. But I don't want to remove it from historical use. That's still important records to keep.
Katie Desjardin
Katie Desjardin
s
sandeep chaudhary
I vote for it. It would be an add on feature to hide old custom fields no longer in use.
Load More
→