This was reported back in 2009 as a known bug, but I have not found any resolution. When I create a custom field of a Single Select dropdown and make it required, it defaults to the first item in the list and will allow it to save even if the default option is left blank. It defeats the purpose of making it a requried field. It treid to create a blank value in the list of choices, but it gets ignored as a value. As a sort of workaround, I have created the first value in the list that says " Please choose an item from the list" but that is a valid choice to the system and will allow the ticket to save with that value. I was directed to an article about creating a custom rulle that would send an email that submitter if the field was not changed, but that still allows the ticket to be created. Any help is greatly appreciated.

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


There is a patch available for this issue. Open a ticket with support.

Answered 01/07/2013 by: jdornan
Red Belt

Please log in to comment



Sorry, I did not indicate in the original post that this is in the Service Desk portion of the K1000 for tickets.

Answered 01/07/2013 by: tomssd
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity