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

Delegating permission management for projects and permission schemes

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.

      Crucible 4.1 introduced "Flexible repository management", which was quite a welcome change. That being said, it does feel incomplete. While it is possible to delegate permission management for repositories, it does not seem to be possible to do so for the projects. It seem that we would need to make all reviews public (including reviews that do not use repository explicitly, but rely on patches instead) to make use of the new feature.

      Is this correct or are we missing something? If it is, would it be possible to introduce similar mechanism to both projects and permission schemes?

      Or maybe projects could be set so that they copy permissions from their default repository automatically?

              Unassigned Unassigned
              b3ea0dbe-e79b-4e98-bc48-1a704c0d395f Deleted Account (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: