Issue description filter's 'none' operator does not match issues with blank descriptions
|Assignee:||Jean-Philippe Lang||% Done:|
Use of the issue description filter with the 'none' operator always returns nothing as it does not include issues with blank descriptions. I think most users expect that issues with blank descriptions are going to be matched when using the filter with the 'none' operator, as such the actual results may be unexpected.
Currently, the 'none' operator only matches issues that are assigned to trackers that have the description field disabled (which is not yet possible with the core, see #25052).
#2 Updated by Marius BALTEANU 2 months ago
- File set_blank_decriptions_to_nil.patch added
From my point of view, there are 2 ways to fix this issue:
1. Set description to nil for all new issues with blank description and migrate all existing issues that have description blank to nil.
2. Change the query for description field in order to check for description is nil or description equals with empty string;
I made a patch that implements the first solution because I think in this way we fix the root cause. The second solution is just an workaround.
If there is any side effect of my solution, I can make a patch with the second fix.
#6 Updated by Marius BALTEANU about 1 month ago
Thanks for your feedback, Jean-Philippe Lang. I've attached a new patch that fixes the issue for text (like description) and string fields. For custom fields, the issue was already fixed.