We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-79542

In JSW Project settings - People - Add People if type the user's email address, it is not checking if the user already exists on the cloud instance or not

      Issue Summary

      In JSW Company Managed Project settings - People -  Add people if type the user's email address, it is not checking if the user already exists on the cloud instance or not. 

      This is reproducible on Data Center: (no)

      Steps to Reproduce

      1. Go to a JSW Project Settings - People - Add People
      2. Type an email address of a user who already exists on the instance for example Faribatest@atlassian.com

      Note: The same issue happens in JSW Team Managed projects Project settings - Access -  Add people

      Expected Results

      It should work the same as JSW and JSM projects and provide just the username because the user already exists on the cloud instance.

      Actual Results

      It returns two possible options:

      • Faribatest
      • Faribatest@atlassian.com

      This is causing confusion. Also, if the user selects their own email address instead of their username it returns the following error:
      We couldn't invite <email address>

      If check the backend logs it generates the correct message:
      "bad-request","message":"User cannot invite themselves"

      Workaround

      Make sure the user has granted the Browse users and groups permission in the Global permission.
      Select the username not the email address unless you know the user does not exist on the instance so must be invited

        1. Screen Shot 2022-07-14 at 11.54.14 am.png
          9 kB
          Fariba
        2. Expected result.png
          16 kB
          Fariba
        3. Actual result.png
          21 kB
          Fariba

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-79542

            In JSW Project settings - People - Add People if type the user's email address, it is not checking if the user already exists on the cloud instance or not

                Issue Summary

                In JSW Company Managed Project settings - People -  Add people if type the user's email address, it is not checking if the user already exists on the cloud instance or not. 

                This is reproducible on Data Center: (no)

                Steps to Reproduce

                1. Go to a JSW Project Settings - People - Add People
                2. Type an email address of a user who already exists on the instance for example Faribatest@atlassian.com

                Note: The same issue happens in JSW Team Managed projects Project settings - Access -  Add people

                Expected Results

                It should work the same as JSW and JSM projects and provide just the username because the user already exists on the cloud instance.

                Actual Results

                It returns two possible options:

                • Faribatest
                • Faribatest@atlassian.com

                This is causing confusion. Also, if the user selects their own email address instead of their username it returns the following error:
                We couldn't invite <email address>

                If check the backend logs it generates the correct message:
                "bad-request","message":"User cannot invite themselves"

                Workaround

                Make sure the user has granted the Browse users and groups permission in the Global permission.
                Select the username not the email address unless you know the user does not exist on the instance so must be invited

                  1. Screen Shot 2022-07-14 at 11.54.14 am.png
                    9 kB
                    Fariba
                  2. Expected result.png
                    16 kB
                    Fariba
                  3. Actual result.png
                    21 kB
                    Fariba

                        Unassigned Unassigned
                        646205eda384 Fariba
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        8 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            646205eda384 Fariba
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            8 Start watching this issue

                              Created:
                              Updated:
                              Resolved: