#5573 closed defect (worksforme)
"is not" option in ticket query not functioning
Reported by: | Owned by: | Matthew Good | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | report system | Version: | devel |
Severity: | minor | Keywords: | query |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The "is not" option in the ticket query does not seem to be functioning. For example, I want all tickets that "are not" a certain milestone. So in the filter I select "is not" from the drop down and pick the desired milestone to exclude and click update. I get no results and the drop down is reset to "is" after refresh. The URL string gets a funky %2521 before the milestone number. If I edit the URL and change the "%2521" to a "!", the query works great.
Attachments (0)
Change History (7)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
I am running 0.11dev-r5849. 0.11dev was not an option in the version list so I picked what seemed to be the appropriate version - devel.
comment:3 by , 17 years ago
Milestone: | → 0.11 |
---|
Did a little more checking and it appears what is happening someone is doing an extra url-encoding. Basically, in the 0.11dev version (currently running r6010), if you use the is not option in the custom query, that item shows in the resulting url with a %2521 in front of it isntead of just a %21 for the !. so someone is converting the ! to %21, and then it is getting converted again which converts the % to %25.
comment:4 by , 17 years ago
comment:5 by , 17 years ago
The contains option is also not working for a text field. Basically, any option that would require passing a special character in the url is not working because it is getting replaced twice so it always has the extra %25 in it.
comment:6 by , 17 years ago
Component: | general → report system |
---|---|
Keywords: | query added |
Milestone: | 0.11 → 0.11.1 |
Owner: | changed from | to
Severity: | major → minor |
Moved to 0.11.1.
comment:7 by , 17 years ago
Milestone: | 0.11.2 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
I've tried to recreate this on current 0.11-stable r7275, and it works like it should for the various dropdowns and text fields I tested.
I'm going to close the ticket as 'worksforme', but please reopen if you can find a way to recreate this on current 0.11 or trunk.
This is working fine on t.e.o. (currently running 0.10.5dev). example 'is not' query
What version are you running?