Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-524

Adding a person or group through the "Add People" button on the board tab shows "Access request sent to your admin" even for admins

    • 1
    • Severity 3 - Minor

      Issue Summary

      Whenever we use the "Add People" button on the board tab for Jira Work Management Team-managed project a pop-up will appear showing "Access request sent to your admin" even if the user performing that is a site/org/project admin.

      The message shows:

      Access request sent to your admin

      Your admin needs to approve access for USER/GROUP.

      The User/Group is added to the project either way.

      Steps to Reproduce

      1. Open a Jira Work Management Team-managed project
      2. Press the "Add People" button on the board tab
      3. Select an existing user or Group from your site
      4. The message "Access request sent to your admin" should be shown
      5. Even though that message pops up, the user is added to the project as expected!

      Using the "Add People" button from the Access page (inside Project Settings) doesn't reproduce the same message:

      Expected Results

      The user inviting others should see the following:

      New people added

      User/Group added to the project. You can also add teammates and manage their access to the project from Project settings

      Actual Results

      The user inviting others sees the following message:

      Access request sent to your admin

      Your admin needs to approve access for USER/GROUP.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available. Use the "Add People" button from the Access page (inside Project Settings) to avoid facing this behavior.

            [JWMCLOUD-524] Adding a person or group through the "Add People" button on the board tab shows "Access request sent to your admin" even for admins

            Atlassian Update - October 16, 2024

            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 - October 16, 2024 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
              976c02b75079 Celso J
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: