Changes between Version 1 and Version 2 of MultiSelectCustomFieldsPatch


Ignore:
Timestamp:
Dec 14, 2010 1:02:08 AM (3 years ago)
Author:
rjollos
Comment:

Escaped CamelCase markup.

Legend:

Unmodified
Added
Removed
Modified
  • MultiSelectCustomFieldsPatch

    v1 v2  
    77This patch allows for multi-select custom fields. They use the same syntax as normal select fields (including '|Option1|Option2' to allow for null values), but display as lists and multi-selects in the ticket profile. 
    88 
    9 This patch tries not to mangle core too much, opting to store Multi-Selects in the database as a pipe-delimited string (e.g. 'Option1|Option2|Option3|'). It uses some magic to display the fields correctly within the ticket profile and in reports. This patch also makes 'contains' work correctly when using TicketQueries by using the pipe ('|') character. 
     9This patch tries not to mangle core too much, opting to store Multi-Selects in the database as a pipe-delimited string (e.g. 'Option1|Option2|Option3|'). It uses some magic to display the fields correctly within the ticket profile and in reports. This patch also makes 'contains' work correctly when using !TicketQueries by using the pipe ('|') character. 
    1010 
    1111== Bugs/Feature Requests ==