- Status Unconfirmed
- Percent Complete
- Task Type Feature Request
- Category Backend/Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 1.0-rc
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#2327 - visibility-option for private tasks
We have some private Tasks in our FS-bugtracker to hide them from normal reporters. But we also have some external beta-testers in a betatesters-group and they should be able to see (and check) the private tasks without giving them a project manager status. So it would be good, if there is a switch in the group option to give specific groups the right to see private tasks.
Loading...
Available keyboard shortcuts
- Alt + l Login Dialog / Logout
- Alt + a Add new task
- Alt + m My searches
- Alt + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + e ↵ Enter Edit this task
- Alt + w watch task
- Alt + y Close Task
Task Editing
- Alt + s save task
Mmh, could be implemented with a new field 'view_private_tasks' in dbtable {groups}
for instance.
What are the permissions of your betatesters for such private tasks? Only view that private task? Shall they be able to view all properties of such private task or only a subset compared to project manager/admin groups?
There are some related tasks yet: FS#1753, FS#2135
Yes, only view the private tasks without any posibility to edit them. We trust the testers, so for us there is no need to limit the private tasks to a subset of properties. But maybe some other users do need this restrictions. So a quick solution could be your suggestion and add some additional restriction possibilities later, when implementing FS#1753 and / or FS#2135
Currently the 'tasks.mark_private' field =1 means, that only following users can view that hidden task:
If we extent the audience of a hidden task to also groups.view_private_summary or groups.view_private_description , I feel we need at least one mark_private possible value:
mark_private=2
The field for mark_private is integer, so no problem and it is easy to adapt the SQL queries to the new feature.
For example
could be changed to
or
And there should be no performance loss.
Having this 2 level of restricting on task level , existing private task do not get immediatly visible to users who had no right to view that existing task.
And you get a different level of decision.
For your example, there could be tasks that you want be visible for your Beta Testers (mark_private=2), but it is still possible to have hidden task that are only accessible for internal staff (mark_private=1).
All in the same project.
What is further needed to change in php sources and templates: