Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-16130

Bulk edit plan permissions fails when group\user name has blank spaces

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • 7.0.0
    • 5.9.1, 5.9.7
    • Permissions
    • None

      Bulk edit plan permissions are failing when group name inherited from JIRA/Crowd has blank spaces.

      Problem

      It's currently not possible to create groups in Bamboo with blank spaces in the name (e.g. Atlassian Support Group). Thus we would have to create a group named atlassian-support-group instead. However, this is not true for other applications like JIRA/Crowd, where it is possible to create groups with blank spaces in their names.

      Problem happens when you have Bamboo using JIRA/Crowd as a user repository: Integrating Bamboo with Crowd. When you are connecting Bamboo to an external user management system, users and groups are no longer coming from Bamboo. Therefore, when Bamboo gets sync'ed with JIRA/Crowd it pulls the groups with blank spaces in their names.

      Steps to reproduce
      1. Set up Bamboo to use Users and groups from JIRA or Crowd: Integrating Bamboo with Crowd.
      2. Add a user to a group with blank spaces in its name (e.g. Atlassian Support Group).
      3. Go to Bamboo administration >> Overview >> Bulk edit plan permissions.
      4. Select a plan which you want to bulk edit permissions.
      5. Set the "Grant permission to" field to "Group".
      6. Select the group with blank spaces in the name (e.g. Atlassian Support Group).
      7. Give the group one of the available permissions (e.g. View, Edit, Build, Clone or Admin).
      8. Hit the Next button.
      9. The following error will be displayed:
      Workaround

      Instead of going to the Bulk edit plan permissions page, access the Plan Configuration >> Permissions page of the plan you're trying to edit permissions, and manually add the group/permissions in that page. That does not trigger any errors and the group is added to the plan's permissions.

            [BAM-16130] Bulk edit plan permissions fails when group\user name has blank spaces

            This bug applies to old versions, that did not use Embedded Crowd.

            Marcin Gardias added a comment - This bug applies to old versions, that did not use Embedded Crowd.

            More low-hanging fruit. I've been a developer for over 30 years, and if this requires more than a half day to fix, I'd eat my hat.

            Deleted Account (Inactive) added a comment - More low-hanging fruit. I've been a developer for over 30 years, and if this requires more than a half day to fix, I'd eat my hat.

            More low-hanging fruit. I've been a developer for over 30 years, and if this requires more than a half day to fix, I'd eat my hat.

            Deleted Account (Inactive) added a comment - More low-hanging fruit. I've been a developer for over 30 years, and if this requires more than a half day to fix, I'd eat my hat.

            I'm seeing this defect in Bamboo 5.12.3.1 build 51215 - 04 Jul 16, and the documented work around no longer seems to be working.

            It would be nice if this got fixed. Mostly because it's sort of an unpleasant surprise to be using a group from Crowd in every one of the other Atlassian Tools and then suddenly run into a problem with Bamboo. It'd be different if these applications were built to elegantly rename groups, but that can't be done and all we can do is destroy the group, recreate it, and redo all of the permissions.

            I do have to admit that I find it troubling that this application has a bug like this arising from a space in a string. This is a pretty common test case.

            Cameron Ackerman added a comment - I'm seeing this defect in Bamboo 5.12.3.1 build 51215 - 04 Jul 16, and the documented work around no longer seems to be working. It would be nice if this got fixed. Mostly because it's sort of an unpleasant surprise to be using a group from Crowd in every one of the other Atlassian Tools and then suddenly run into a problem with Bamboo. It'd be different if these applications were built to elegantly rename groups, but that can't be done and all we can do is destroy the group, recreate it, and redo all of the permissions. I do have to admit that I find it troubling that this application has a bug like this arising from a space in a string. This is a pretty common test case.

              Unassigned Unassigned
              brosa Bruno Rosa
              Affected customers:
              4 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: