When defining eligible values for a ticket field of type select, it is currently impossible to define any values that contain whitespace characters. All whitespace characters are used as delimiters for the select values. Workarounds such as hyphens or underscores have to be used to indicate two separate words.
There are various ways how whitespace could be supported:
~) to indicate that two or more words belong together, and displays a whitespace instead.
In the context of the ticketing system, I think suggestion 3) is the most straightforward solution, even though it would mean one character, e.g.
~, cannot be used any more.