•  
      story #13237 Prevent restricted to be added to private projects
    Summary
    Empty
    Prevent restricted to be added to private projects
    Empty

    Follow-up to story #12554

    • Project admin can no longer add restricted users to project members (and user groups)
      • Users are not proposed in autocompletion
    • When a user is switched to restricted, the user is removed from all projects that are "private w/o restricted" (and all user groups)
      • There is a warning message to confirm the action (User is going to be removed from X projects).
    • When a project is switched to "private w/o restricted", all restricted users are removed from project members (and all user groups)
      • There is a big warning message specific to this switch to confirm (when there are restricted): "X users are going to be removed from this project".
    • Binding of user groups must filter restricted users when target group is a "private w/o restricted" project.
    • On LDAP sync of user groups, the users are filtered to remove restricted that should land in "private w/o restricted" project.
      • Warning, user filters (that control how users are created/updated on the platform from LDAP) must be applied before the "private w/o restricted" filter.
    • The 4 level of project access must be managed a project creation
      • Should be proposed in the web UI
      • Should be managed as default value for project creation
        • The local.inc config "$sys_is_project_public = 1;" is put in the DB (and can manage de 4 possible default values) and managable by the web ui and "tuleap set-config" CLI
    Empty
    Empty
    Status
    Empty
    Done
    Development
    • [x] Does it involves User Interface? 
    • [x] Are there any mockups?
    • [x] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #13237
    Nicolas Terray (nterray)
    2019-04-30 14:11
    2019-04-07 00:52
    4189

    References
    Referencing story #13237

    Git commit

    tuleap/tuleap/stable

    SOAP API can handle accesses to resources in private projects without restricted users dd1bfc200e
    Project admin user autocompleters do not show restricted users when the project is private without restricted 188b95c5b4
    Crash when accessing statistics plugin data via the SOAP API f8644ef489
    Sync of the project members to an LDAP directory group is aware of the restricted status 5e1a5a2f1d
    Mostly fix Project.class.php style 26c47fe11d
    Restricted user cannot be added to project in the 'private without restricted mode' dda39bbbb1
    Remove restricted users from project to be private without restricted 099dae8a94
    Cleanup ProjectUGroup class (style and docblock type annotations) 969317c76a
    Memberships to private without restricted project are removed when a user becomes restricted 3ae770b2a8
    Add a content hash on the ressources of the TLP UI framework 0a33f623f7
    It is possible to choose if a project allows restricted users at the creation 8a8d5e1353
    Default project visibility can now be set through the Tuleap CLI b645301289
    Introduce a setting allowing to use all project visibility mode 739f2460c6
    Remove 'private without restricted' feature flag fcf543ac9c
    Fix typo in the warning message about restricted users and project visibility 521ca4e495
    Default project visibility can be modified in the siteadmin web UI 5ae4ee78be
    Stop autosubmitting site admin form about project visibility 4cd6cdaa06
    Mention in the warning message that the removal of restricted users is not immediate da89298b5a

    Follow-ups

    User avatar
    • I want to
      -Introduce new level of visibility (private without restricted) 
      +Prevent restricted to be added to private projects 
    • So that
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Acceptance criteria
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes