Defect #980
"For all projects" custom queries
| Status: | New | Start date: | 2008-04-03 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Issues | |||
| Target version: | - | |||
| Affected version: | devel | Resolution: |
Description
I have setup several custom queries and marked them as "For all projects".
The first time I view this query, it works great. If I then select one of the issues in the list, then click on the custom query again, the issue list is restricted to just the issues in the project of the current issue. ie, it doesn't show all issues for all projects. If I go back out to "My page", click on "View all issues" under "Issues assigned to me", then click on the custom query again, it lists everything again.
I am running 0.7.devel.1315 on:
ruby 1.8.5 (2007-06-07 patchlevel 52) [i386-linux]
Rails 2.0.2
Related issues
History
#1 Updated by Carl Nygard about 4 years ago
Look here to get a proper explanation of "For all projects", which only means that the query shows up in the query list on all projects across your Redmine installation. The behavior you noted is correct, if you are on "My Page" then you have a "global" scope for your query operation. If you view one of those issues, then you are now looking at an individual project, and you now have a "project" scope for your query operation.
#2 Updated by Paul Macdonnell about 4 years ago
If that's the way they're supposed to work, that's ok, I just would have thought it would have kept a global scope to include all issues rather than switch to a project scope. That's just how I envisioned it working.
I would have liked to have been able to click on my custom query again (when viewing an issue) and go back to the global list, that way I can keep working with the same set of issues, without have to get out of the project scope. Is there an easier to switch from project scope to global scope, other than going back through "My page" -> "View all issues" (in "Issues assigned to me") -> click my custom query?
It just seems counter-intuitive to me.
#3 Updated by Milton Taylor about 4 years ago
I agree with Paul...this aspect probably needs a litle more fleshing out in Redmine.
#4 Updated by Mischa The Evil over 2 years ago
Added issue relation to #1495.
#5 Updated by Brian Heasley over 1 year ago
I agree that this is an odd counter-intuitive behavior. I'd love to see an option to allow a custom query to be global in scope anywhere it appears. It is convenient to have the report appear when I am looking at a project, but I still want to it to be global in scope anytime it runs.
#6 Updated by Sebastian M 11 months ago
Just a +1... I like the idea of the current "for all projects" functionality, but it is confusing for people who open a query that is designed to be run at a global scope, and it's not showing all records.
Some better visual indication including a link to pull out to global scope would be good.
#7 Updated by Bryan Greenaway 6 months ago
My company was running a very old redmine version 0.9.1 where no matter what issue/project you were viewing when you click a custom query it would run it globally. I still have all the source code backed up but I can't find where in the code this is happening, as I am very new to Ruby. Could someone let me know where the code that build the custom query URL is located so I can compare it with the legacy source code I have? If I find a solution I would be happy to update the community with it.
#8 Updated by Fernando Hartmann 5 months ago
+1 this is must be feature !
The path "My page" -> "View all issues" -> "Global Query" is too long !