Ticket #4382 (closed defect: fixed)
Opened 5 years ago
Last modified 2 years ago
&- character in ticket type with custom queries
| Reported by: | anonymous | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | report system | Version: | 0.10.2 |
| Severity: | normal | Keywords: | query |
| Cc: | |||
| Release Notes: | |||
| API 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
Change History
comment:1 in reply to: ↑ description Changed 5 years ago by cboos
- Milestone set to 0.10.4
comment:2 Changed 5 years ago by anonymous
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 Changed 4 years ago by cboos
- Keywords query added
- Milestone changed from 0.10.5 to 0.12
- Owner changed from mgood to cboos
- Severity changed from trivial to normal
Problem happens also with query: links and TicketQuery ...
comment:4 Changed 3 years ago by cboos
- Milestone changed from 0.13 to 0.11.4
comment:5 Changed 2 years ago by cboos
- Milestone changed from 0.12.1 to 0.12
- Resolution set to fixed
- Status changed from new to closed
Fixed in [8630].
Replying to anonymous:
Yep, I've noticed that already while testing "&" in milestones, same problem.