Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-78094

Group name is not listed in drop-down list if there are too many similar entries

      Summary

      In the drop-down list of the permission scheme when granting permission to a specific "Group" OR when granting Global permissions OR project roles, if there are too many group entries with the same group name, the drop-down only lists the first 20 group matches.

      For example, if you tried to search group "user" and you have multiple groups named a-user, b-user, c-user, and so on. The list will be limited to the alphabetical descending results in the drop-down. The list is also limited to only showing 20 out of the total groups, therefore, if the specific group you're after is not in the first 20, you wouldn't be able to select it.

       

      Steps to Reproduce

      1. Create multiple groups with similar names, (user, a-user, b-user, c-user, etc..)
      2. Make sure the total number of groups following the above criteria is above 20.
      3. Go to a permission scheme > Click on Edit on any permission > Choose "Group" > On the column, type "user".
      4. The list will only consist of the first 20 results alphabetical from a-user all the way to the last result, which will not consist of "user".

      Screenshot:

       

      Expected Results

      When a user enters the group name, the drop-down list does provide the required group when searching. 

      Actual Results

      The drop-down list does not provide the exact group name.

       

      Workarounds

      Type the group name with caps lock for the first letter, for example for the group "users", search with "Users", the results comes out. 

        1. error-part-1.png
          error-part-1.png
          46 kB
        2. error-part-2.png
          error-part-2.png
          47 kB

          Form Name

            [JRACLOUD-78094] Group name is not listed in drop-down list if there are too many similar entries

            Atlassian Update - December 29, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - December 29, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              e32c3a85cf21 Uchechi I
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: