| Reporter |
Roman Kolobov (rekolobov)
|
|---|---|
| Created | Jul 26, 2013 5:11:04 PM |
| Updated | Jul 26, 2013 6:28:01 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Alexander Volfman (Alexander.Volfman) |
| Subsystem | Issue Search Context |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | 4.2, 5.0 |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Undefined |
1. Create a saved search with the name containing both a space and a closing curly brace (e.g. State: {Won't fix}) (the query itself doesn't matter, it just shouldn't be erroneous itself).
2. Try to set it as a search context.
Instead of search results, an error message appears.
The search itself, however, when called from the "Saved searches" sidebar list, works fine.
Also, the left brace in the name doesn't cause this problem, it's only the right one which leads to the error.
Given that there already are some symbols prohibited in search context names [<>&,], I'd rather expect braces to be illegal as well.
2. Try to set it as a search context.
Instead of search results, an error message appears.
The search itself, however, when called from the "Saved searches" sidebar list, works fine.
Also, the left brace in the name doesn't cause this problem, it's only the right one which leads to the error.
Given that there already are some symbols prohibited in search context names [<>&,], I'd rather expect braces to be illegal as well.