Flyspray - The bug killer!

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Documentation
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version 1.0-rc9
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Olivier Humbert - 01.09.2019

FS#2568 - [MANUAL] a missing image in "Understanding Permissions: Group Permissions"

In the page http://www.flyspray.org/manual/group_permissions/ , it is written

Shown is an image of the permissions page for the Flyspray project’s Contributors group

but there is no image in there.

I can think of two ways of dealing with that I guess:

  1. add an image
  2. remove the sentence

What do you think?

Project Manager
peterdd commented on 02.09.2019 04:46

3. rewrite the user permission manual :-P

The permission manual was written before I appeared on the Flyspray project.

I think there should be only one page talking about the permission system. It should contain screenshots how practical configurations could be as a guide. (Here feedback from people from bigger communities like lede/openwrt or archlinux could help)

Should at least contains these 2 screenshots:

  • One for 'use only global groups' for all projects
  • and One for 'minimal global groups and global group permissions, and configure groups for each project'
  • The resulting permissions of a user can be viewed on the ?do=myprofile page. This page does not yet has the same icons as on the global and project configuration pages. And there is no masquerading feature yet where admins could impersonate/browse Flyspray as a less privileged user to verify if permission system is configured correct for that user.

I tried to bring global and project permission configuration more together in the user interface. At least admins now can see the global group configurations on the same page beside the groups of a project.
It looks currently not very fancy, but shows what was hidden in older Flyspray versions like overrides by general project configuration.

Some of project settings ( project_is_active , others_viewroadmap , others_view, anon_open , comment_closed , freetagging ) effect also the resulting permissions of a user in a project. Some settings could move from

index.php?do=pm&area=prefs&project=1

to

index.php?do=pm&area=groups&project=1

but not yet sure which.

I related FS#1950 and FS#2561 with this task as they show some changes since 2014.

The 'view groups task'-permission is too ambiguous and without function and get probably removed. At least I do not how that should work because currently a task can only be assigned to a user, not a group. And looking in the database to find the other users of all the assignees who are in same user groups of the assignees is too wacky and begs for subtil issues in the long run I think.
That feature probably requires database schema changes to make it right like assign a task directly to a group or team(s). Not in near future.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing