You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario: There are several Flyspray 'projects'. Some are related, some are complete different.
Current
Either user selects a project, then search there. User selects another project and search there, ...
or
Select the 'All Projects' task list and do a search across all projects the user has 'View Tasks' (global or per project) permission (minus 'private' marked tasks if not privileged (Admin/ProjectManager) project user).
or
Sure, there is always possible that privileged people with direct access to the database could do their own SQL-query bypassing any Flyspray permission settings or build their own enhancement/plugin to show somewhere.
Wish
User would like to do a search across multiple related projects the curent user has 'View Tasks' permission to for the selected projects.
Well, this also lead to another idea of enabling configuring a relation between projects.
If it could be grouping, a super-sub relation, treelike or other is completely open and not in near future. I just post it as an idea here too.
The text was updated successfully, but these errors were encountered:
Scenario: There are several Flyspray 'projects'. Some are related, some are complete different.
Current
or
or
Sure, there is always possible that privileged people with direct access to the database could do their own SQL-query bypassing any Flyspray permission settings or build their own enhancement/plugin to show somewhere.
Wish
User would like to do a search across multiple related projects the curent user has 'View Tasks' permission to for the selected projects.
Well, this also lead to another idea of enabling configuring a relation between projects.
If it could be grouping, a super-sub relation, treelike or other is completely open and not in near future. I just post it as an idea here too.
The text was updated successfully, but these errors were encountered: