Opened 18 years ago
Closed 15 years ago
#4382 closed defect (fixed)
&- character in ticket type with custom queries
| Reported by: | anonymous | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | report system | Version: | 0.10.2 |
| Severity: | normal | Keywords: | query |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
If ticket type value has &-character, for example 'q&a', custom query filter does not work correctly.
When I first add type filter to custom query, the drop down box has value q&a. If I click update button, query finds nothing, and type value in drop down box is corrected to q&a. After that the query works correctly: it finds 'q&a' tickets and filter drop down box has correct value.
Wrong value in type filter appears only when type filter has been just added.
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
| Milestone: | → 0.10.4 |
|---|
comment:2 by , 18 years ago
The problem is that the HTML entities like & don't mean anything to JavaScript, so when query.js gets the option name it doesn't convert & back to &. Not sure what to do about this though…
comment:3 by , 17 years ago
| Keywords: | query added |
|---|---|
| Milestone: | 0.10.5 → 0.12 |
| Owner: | changed from to |
| Severity: | trivial → normal |
Problem happens also with query: links and TicketQuery …
comment:5 by , 15 years ago
| Milestone: | 0.12.1 → 0.12 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Fixed in [8630].
Replying to anonymous:
Yep, I've noticed that already while testing "&" in milestones, same problem.