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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Gathering Impact (View Workflow)
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: 5.9.1, 5.9.7
    • Fix Version/s: None
    • Component/s: Permissions
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              brosa Bruno Rosa (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated: