8

1

I am adding a dropdown custom field to my cases, but I want to have it as an "optional" field for the user to capture and fill. I've tried in vain, but can't seem to add a blank as the first option so that the user can hide the field and review it at their convenience.

Example: I have a list of applications where the user is experiencing a problem "MS Word", "MS Excel", "Web Mail". I'd like to make the field optional on the left to include in the case.

Fog Creek Case FC1833465

flag
I too would greatly like to have this ability. We have a custom field because a large portion of our cases need it, and it needs to be a discrete value from a limited set, but not all cases need this field. The custom drop-down works perfectly fine (in our case a check-box list would better) for the cases that need it, but it is just useless clutter for those that don't. – cdeszaq Mar 9 2010 at 16:23

3 Answers

1

Currently, the custom field plugin trims each entry (i.e. strips any spaces at the beginning or end of the drop down value) and then discards any blank entries that are left.

So, to answer your question, no, there isn't currently a way for a custom dropdown field to contain a blank option. There is a case open for this though, so I've updated that case with a note to update this question when it has been implemented.

link|flag
Is there a case number or a link where we can see status? I tried using an html entity to "fake" a blank value ( ) and i just ended up with the straight entity text. – Caio James Feb 15 2010 at 21:48
A blank option for Custom Fields is really needed. For instance, my Customer Care Team don't need the visual clutter of the Technical Support Team's custom fields, and vice versa. – Justine Oct 14 2010 at 13:17
0

I would just use something like "-" or "--none--"

link|flag
I am using N/A in the mean time -- but blank would be preferrable. – Caio James Feb 18 2010 at 21:17
Understandable. We have a case open to consider adding this feature in a future release. Thanks for the feedback! – adambox♦ Feb 19 2010 at 15:56
Your suggestion can work, but it's hacky and it adds noise to the grid. We need: 1. Allowance for an empty/blank option. 2. Recognition of nullable dropdown fields by the UI, so that they can be hidden when they lack a value, like any other field. Now, the user may elect not to supply an empty option, but it should be just that: the user's choice. Thanks! – Grip Apr 2 at 0:09
0

A "blank" value would work perfectly for me.

link|flag

Your Answer

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