#9839 closed defect (wontfix)
Pipe is not appended to single option
Reported by: | Jan Beilicke | Owned by: | CM Lubinski |
---|---|---|---|
Priority: | normal | Component: | MultiSelectCustomFieldsPatch |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.12 |
Description
I just noticed that some queries didn't return all matching tickets. At first I thought it might be caused by old data, that was not updated (see also #9731). It turned out, that every update to a ticket (ticket properties or comments) removes the pipe of single options again.
When the multi had more than one selected options (which worked fine) and all but one options are removed, the remaining option is stored without a pipe.
I assume that the pipe is simply not set in the model.py __setitem__()
where isinstance(value, list)
is processed - maybe the value isn't a list anymore?
Feedback is highly appreciated. :)
Attachments (0)
Change History (2)
comment:1 Changed 13 years ago by
Summary: | Pipe is not appended for single options → Pipe is not appended to single option |
---|
comment:2 Changed 11 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
TracMultiSelectBoxPlugin is pretty good. I'm going to mark this plugin as deprecated in favor of that one, or MultiSelectFieldPlugin, which I haven't looked at.
After some investigation I came up with the following patch. It contains the original MultiSelectPatch (only model.py) plus a quick fix for my issue, applied in
populate()
:ticket/model.py
raise TracError(_("Multi-values fields not supported yet"))So far it seems to work, the pipe gets (and stays) appended to single values.