Flyspray

  • Status Confirmed
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version 1.0 devel (github master)
  • Due in Version 1.1 devel
  • Due Date Undecided
  • Votes 2
  • Private
Attached to Project: Flyspray
Opened by Josh - 20.06.2012
Last edited by peterdd - 09.03.2015

FS#1753 - Usergroup Restriction: Only View Summary

I was really impressed with Flyspray and about to use it as our bug tracker, but then I discovered quite a big problem. You can't restrict users from seeing full task details.

I would really love the ability to let them only see the summary. My reason being is that I'm needing a bug tracker for my game, and bugs reported can be easily abused, and will be abused, if people can just read bug reports and see how to replicate them.

The reason I don't like just unchecking the "View Tasks" option, is because they wont be able to see if there is already a task about the bug, so we would just get flooded with duplicate reports on the same bugs.

Project Manager
Psychokiller1888 commented on 07.03.2015 06:25

FS 1.1 maybe

Project Manager
peterdd commented on 09.03.2015 13:19

Removed second part of the original feature request, which is now handled by FS#1950.

Project Manager
peterdd commented on 27.10.2015 10:22

Hello Josh, I understand your requirement.

Flyspray works as "permission system only" on global and project level.

  • So one possibility would be to drop the "View Task" permission from the 'Basic group' or what groups you use for your customers and give them a "View Task Summary" permission? (global or per project level depends on your usage)
  • Or let the "View Task" permission just do not include the task description permission, so in effect a "View Task Description" must be ticked too to view the description?

Maybe the second is easier to implement. Checking the "View Task Description" permission on template output for Task Details View, Task List View, Top Level View, ...?
How to avoid slowing down on global task lists? E.g. one project allows description, another not, so we must check for every drawn task.
The get_task_list in class.backend.php currently selects all fields of a task by t.*

But how all then the other fields should be handled?
Should it allow to view task type, priority, severity, progress, assignees..?
Ok, I think this goes too far, lets just do task details permission.

Project Manager
peterdd commented on 27.06.2016 18:54

I related FS#2135 with it, because the problem there leads to a similiar thing:

different access levels for task fields for different flyspray user groups.

Without doubt, we/I could extend Flyspray to have such fine granulary permission monster. But also important is that it still is easy managable.

As fixing FS#2135 is important to be fixed with other things like 'updatetaskchecks', 'movetaskchecks', chances rise this feature is coming somedays ..

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing