Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-8119

Change permission schemes so that they can be applied to multiple projects

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hello Atlassian Developers,

      while configuring new projects on our crucible server it occurred to me that setting up permission schemes is rather cumbersome at the moment.

      The non-disclosure agreements in the contracts with our customer demand that only the team of a project has access to the corresponding project data. Thus at the moment we create an individual permission scheme for every project.

      All permission schemes are exactly the same except for two fields. In the fields "view" and "create" the project groups are entered because I did not find a different way to only give the project team access to the project. It would be great if there would be a role called for example "allowed review participants" that grant everyone who is entered in the project settings permission to view and create reviews.

      That way we could use the same permission scheme for every project on our server. It would save a bit of work. At the moment I have to enter the same group in the project settings, permission scheme and repository permissions of every project. So at the moment the permission scheme is just redundant for our usecase.

      Best regards

      Leonard

              Unassigned Unassigned
              8bcbf905a4e3 L. Schimmel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: