Feature #23301


Allow "Custom queries" to be shared across projects

Added by @ go2null about 8 years ago. Updated almost 5 years ago.

Issues filter
Target version:
Start date:
Due date:
% Done:


Estimated time:


A sharing mechanism like Versions would be great.

Actions #1

Updated by Jean-Philippe Lang about 8 years ago

  • Status changed from New to Needs feedback

Administrators can make queries visible in all projects. Do you need a finer-grained sharing system?

Actions #2

Updated by Carlos William Dias Peixoto about 7 years ago

When the query filters by a custom field not set for all projects, turning it into a global one erases the field. This feature would allow sharing such queries across the projects who uses such custom fields.

Beyond sharing them like versions, it would be nice to list the projects where the query would work. However, this could become an administrative nightmare if one site has too many projects (mine have over 700!). Alternative: show global queries only where all filtered fields are available.


Actions #3

Updated by Toshi MARUYAMA about 7 years ago

  • Status changed from Needs feedback to New
Actions #4

Updated by @ go2null over 6 years ago

Good comment about global queries dropping non-global fields.

The original intent of this request was to allow sharing like Versions, that is, Subprojects, Hierarchy, and Tree. (With the Subprojects@ and Hierarchy being the more useful ones.)

Actions #5

Updated by Stephane Evr about 6 years ago


Actions #6

Updated by Yuuki NARA over 5 years ago


I think that allow sharing like Versions is best way,

As a method of simplifying implementation,
I think that queries defined in the top project may be displayed unconditionally.
In this way, you do not have to modify the Database.

By the way,
the function of category also has the same problem. I created a patch below.

Actions #7

Updated by Yuuki NARA about 5 years ago

I changed some code of Redmine and tried to create a countermeasure.

Considering the actual operation, I think there are the following two issues.

1.Use authority setting of custom query shared among PJ.
2. Create/ Edit shared amaong PJ Custom Query (except admin)

1.Use authority setting of custom query shared among PJ

This can be achieved by using role-based custom query access control, enabling all projects, and assigning a role to each project.
(This feature is introduced in Redmine 2.4.0, so there is no need to develop new features.)

2. Create/ Edit shared amaong PJ Custom Query (except admin)

Another issue is that only admin can create and edit custom queries shared among PJs.
I created a workaround patch for this issue by assigning the custom query create/edit privilige , the same all custom PJ target as admin to the custom query author.

Please refer to the following for details.

However, in principle, it is considered appropriate to set permissions in System level Role.

I am glad if it helps.

Actions #8

Updated by Geoffrey Bailly almost 5 years ago



Also available in: Atom PDF