| 1 | | I noticed we allow duplicate keywords (same behavior on 1.0-stable). To avoid duplicates, I'd propose that we define a separator (could be configurable using an option `[ticket]` `list_separator`), parse the list field with separators `;,\s` on ticket save, store the values in the database as a whitespace-separated string, and join the fields using the defined separator when rendering. |
| | 1 | I noticed we allow duplicate keywords (same behavior on 1.0-stable). To avoid duplicates, I propose that we define a separator (could be configurable using an option `[ticket]` `list_separator`), parse the list field with separators `;,\s` on ticket save, store the values in the database as a whitespace-seperated string, and join the fields using the defined separator when rendering. I don't plan to propose any of those changes in this ticket. |
