Opened 6 years ago
Last modified 3 years ago
#13185 new enhancement
Keywords: remove duplicates and fixup separators
| Reported by: | Ryan J Ollos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-dev-1.7.x |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | keywords |
| Cc: | clemens.mosig@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
In comment:16:ticket:13179, the following changes to the keywords field were proposed:
- Fixup separators. Example:
kw1, kw2; kw3 kw4→kw1, kw2, kw3, kw4(or use whitespace rather than comma separators). This would match the behavior for the CC field. - Remove duplicates.
Attachments (0)
Change History (6)
comment:1 by , 6 years ago
| Milestone: | next-major-releases → next-dev-1.5.x |
|---|
comment:2 by , 5 years ago
| Milestone: | next-dev-1.5.x → next-dev-1.7.x |
|---|
comment:3 by , 3 years ago
Do we want to change this only for new keywords that are entered or do we also need to change the existing database?
comment:4 by , 3 years ago
| Cc: | added |
|---|
comment:5 by , 3 years ago
From comment:16:ticket:13179:
parse the list field with separators
;,\son ticket save, store the values in the database as a whitespace-seperated string
I agree with this. Save it whitespace-separated. Allow people to write , and ;, but remove them on store. I don't see a need to change existing database entries proactively except when a user triggers a change to the field.
comment:6 by , 3 years ago
Currently, _fixup_cc_list method fixes up cc field on creating and updating ticket record. At least, it is needed to do the same to keywords field as well.
Milestone renamed