Uploaded image for project: 'Red Hat Decision Manager'
  1. Red Hat Decision Manager
  2. RHDM-1309

Branch management doesn't work when a group is configured as a contributor

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 7.7.0.GA
    • Decision Central
      • Red Hat Decision Manager (RHDM);
      • Red Hat Process Automation Manager (RHPAM);
    • Hide

      1 - Create a group - for instance: 'group-dev';
      2 - Associate to an user - for instance 'testUser'
      3 - With admin user, in security-management give read permission to 'group-dev' group;
      4 - Set the 'group-dev' as contributor on space contributors setting;
      5 - Also set the 'group-dev' as contributor on project contributors settings;
      6 - On project Branch Management settings, set only read permission to Contributor on Master branch;
      7 - Also give to Contributor read/write permission to Dev branch.

      Show
      1 - Create a group - for instance: 'group-dev'; 2 - Associate to an user - for instance 'testUser' 3 - With admin user, in security-management give read permission to 'group-dev' group; 4 - Set the 'group-dev' as contributor on space contributors setting; 5 - Also set the 'group-dev' as contributor on project contributors settings; 6 - On project Branch Management settings, set only read permission to Contributor on Master branch; 7 - Also give to Contributor read/write permission to Dev branch.
    • 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4)

    Description

      When a group is configured as a contributor, the branch management configuration doesn't apply. The group settings supersede the branch management configuration. This doesn't occur when an user is configured as a contributor.

      Attachments

        Issue Links

          is documented by

          Task - Represents a small unit of work that is not end-user facing. BXMSDOC-5810 Document: Branch management doesn't work when a group is configured as a contributor

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              r_anand Rishiraj Anand
              rhn-support-bkramer1 Biljana Kramer
              Barbora Siskova Barbora Siskova
              Barbora Siskova Barbora Siskova
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: