Defect #9108
closed
Custom query not saving status filter
0%
Description
When creating a custom query, its default is to save the Status filter to "open", disregarding whether I disable it to get all statuses. In order to create this custom query properly, I have to save it, and after that change the status filter again.
To reproduce:
1. Go to issues list and click "Save" to create a custom query.
2. Uncheck the "Status" filter, so it would show all statuses, and save the query.
3. Note that the query is STILL showing only issues with status "Open".
4. Edit the custom query and uncheck the "Status" filter again.
5. Note that the query is now showing all issues correctly, with no status filter.
I think that the expected behavior would save the unchecked "Status" filter on the first try.
My version is 1.1.1, but this also happened on the online demo.
Related issues
Updated by Etienne Massip over 13 years ago
- Target version set to Candidate for next minor release
- Affected version (unused) changed from 1.1.1 to 1.2.1
- Affected version changed from 1.1.1 to 1.2.1
Indeed, in the New query screen, RM lists the Status field even if this one was unchecked.
Even if you can uncheck it again from this screen before you save the query, this does not happen to other fields, hence the bug.
Kind of same issue as #8411, I guess.
Updated by Etienne Massip about 13 years ago
- Status changed from New to Resolved
- Target version changed from Candidate for next minor release to 1.3.0
- Resolution set to Fixed
Should be fixed with r7649 which is too big to be included in a minor release.
Updated by Etienne Massip about 13 years ago
- Status changed from Resolved to 7
- Assignee set to Etienne Massip
- Resolution deleted (
Fixed)
Ok, there is a big bug now with handling project, will fix it tonight.
Updated by Etienne Massip about 13 years ago
- Status changed from 7 to Resolved
- Resolution set to Fixed
Should be clean now with r7657.
Updated by Mischa The Evil about 13 years ago
Updated by Etienne Massip about 13 years ago
Mischa The Evil wrote:
Confirmed!
Thanks. So glad to see you here again, Mischa =)
Updated by Etienne Massip about 13 years ago
- Status changed from Resolved to 7
Something must have gone wrong: .
Updated by Etienne Massip about 13 years ago
- Status changed from 7 to Resolved
Etienne Massip wrote:
Something must have gone wrong: .
Finally, seems to be only plugin issues.
Updated by Etienne Massip about 13 years ago
- Status changed from Resolved to 7
There might be some remaining Queries permissions work to go in source:/trunk/lib/redmine.rb@7819#L81.
Updated by Etienne Massip about 13 years ago
- Status changed from Closed to Reopened
- Resolution deleted (
Fixed)
Still not fixed according to #9738.
Updated by Jean-Philippe Lang about 13 years ago
- Status changed from Reopened to Closed
- Resolution set to Fixed
Not related to #9738 and it can not be reproduced.
Updated by Etienne Massip about 13 years ago
#9738 has appeared after the query refactoring committed for this issue.
Updated by Marius BĂLTEANU almost 7 years ago
- Related to Defect #28264: Global and public custom queries are shown as editable to non administrators in projects added