Public custom queries when not admin.
Added by Joel SCHAAL over 10 years ago
Hello,
We recently removed the admin rights for all project managers, and use now the default possibilities.
But we also used the custom queries with public visibility a lot, and those seem not to be accessible per default when you are not admin.
What am I doing wrong ?
Replies (3)
RE: Public custom queries when not admin. - Added by James H over 10 years ago
allow "all users" to view or use the custom query while creating or editing it, if you havnt already
RE: Public custom queries when not admin. - Added by Joel SCHAAL over 10 years ago
OK I understand better what I was doing wrong.
If I create a custom query for all project (so not related to a particular project) when I am in a project where I have manager rights I get that:
But when I do the same on a project where I don't have those rights, this is what I get:
So why does the source project have an impact on how the query can be viewed if it will not be attached to it ?
I think we should need global rights (rights not relative to a particular project), so we would be able to create and modify public custom queries easily. Because as of now I get a 403 if I want to edit a custom query for all project visible to all users. Even if I was the one that created it. The same applies if I want to delete it.
without_rights.png (2.31 KB) without_rights.png | |||
with_rights.png (7.73 KB) with_rights.png |
RE: Public custom queries when not admin. - Added by James H over 10 years ago
think the main thing is
if you are not an admin - you cannot choose which users can see your query, the query is your own personal query, whether or not it is available for that specific project you are in or "For all projects" is a separate issue.
if you are an admin - you can choose which users can see your query, meaning that you can choose whether or not the query you are creating is a "personal" query or a "public" query.