Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-766

Based in (location) cannot be updated via user provisioning

XMLWordPrintable

      Issue Summary

      When connecting Atlassian Access to a third party identity service provider, the Based In (location) attribute of an Atlassian Account cannot be updated.

      Steps to Reproduce

      1. Enable Atlassian Access setup user provisioning
      2. Try to map a location attribute from the third party IDP into the location attribute in Atlassian.

      Expected Results

      It should be possible to map the location attribute into the Atlassian Account

      Actual Results

      The location attribute of a user cannot be mapped.

      On the managed account profile, the location attribute is blocked due to user provisioning

      Workaround

      The provisioned users can still fill in the details on Atlassian side.

        1. based in.png
          based in.png
          67 kB
        2. image-2021-05-21-12-24-18-735.png
          image-2021-05-21-12-24-18-735.png
          206 kB
        3. location.png
          location.png
          113 kB

          Form Name

            [ACCESS-766] Based in (location) cannot be updated via user provisioning

            Aneita made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Aneita added a comment -

            Hi all,

            'Based in' is not currently a field that can be updated via SCIM. We have an open feature request to support this, so I'm closing this ticket as duplicate of ACCESS-822. Please vote for / watch that ticket for updates. 

            We are currently conducting customer interviews to better understand use cases and expectations for additional SCIM attributes. If you are interested in sharing your thoughts, please send me an email at ayang@atlassian.com and we can schedule a time to chat. 

            Cheers,

            Aneita

            Aneita added a comment - Hi all, 'Based in' is not currently a field that can be updated via SCIM. We have an open feature request to support this, so I'm closing this ticket as duplicate of ACCESS-822 . Please vote for / watch that ticket for updates.  We are currently conducting customer interviews to better understand use cases and expectations for additional SCIM attributes. If you are interested in sharing your thoughts, please send me an email at ayang@atlassian.com and we can schedule a time to chat.  Cheers, Aneita

            Léo Boulanger added a comment - - edited

            Totally agree that it is needed to be able to sync a user location into Atlassian users. We are present in 19 countries and use Altassian as a helpdesk. We can not ask a couple thousand users to fill out their Atlassian Account themselves, and when having to double-check the Users Location in other Systems just costs to much valuable time.
            Sadly it's not the only bug that should have been a standard feature.

            @Sudesh Peram can we get some kind of update here?

            Léo Boulanger added a comment - - edited Totally agree that it is needed to be able to sync a user location into Atlassian users. We are present in 19 countries and use Altassian as a helpdesk. We can not ask a couple thousand users to fill out their Atlassian Account themselves, and when having to double-check the Users Location in other Systems just costs to much valuable time. Sadly it's not the only bug that should have been a standard feature. @Sudesh Peram can we get some kind of update here?
            SET Analytics Bot made changes -
            Support reference count Original: 30 New: 31
            SET Analytics Bot made changes -
            Support reference count Original: 31 New: 30
            Narmada Jayasankar made changes -
            Assignee Original: Narmada Jayasankar [ njayasankar@atlassian.com ] New: Sudesh Peram [ e902c0832f88 ]
            SET Analytics Bot made changes -
            Support reference count Original: 29 New: 31
            SET Analytics Bot made changes -
            Support reference count Original: 28 New: 29
            SET Analytics Bot made changes -
            Support reference count Original: 27 New: 28

            Tobias H added a comment -

            Disheartening to see a comment from 2019 having the exact same issue as I am trying to solve today.

            This should be a high prio issue, as it's clearly not working as intended.

            I added a Location mapping in Okta and synced it towards the location string provided in the Atlassian Cloud app, but nothing happened.
            One would expect this (or any of the other fields) to populated the Based In field within Atlassian.

            Currently we have an estimate of 5%~ users with their location set, so our support agents need to cross check with our HR system where an employee is based and not just from hovering their profile picture on the Reporter field :/

            Tobias H added a comment - Disheartening to see a comment from 2019 having the exact same issue as I am trying to solve today. This should be a high prio issue, as it's clearly not working as intended. I added a Location mapping in Okta and synced it towards the location string provided in the Atlassian Cloud app, but nothing happened. One would expect this (or any of the other fields) to populated the Based In field within Atlassian. Currently we have an estimate of 5%~ users with their location set, so our support agents need to cross check with our HR system where an employee is based and not just from hovering their profile picture on the Reporter field :/

              e902c0832f88 Sudesh Peram
              rmacalinao Ramon M
              Affected customers:
              71 This affects my team
              Watchers:
              74 Start watching this issue

                Created:
                Updated:
                Resolved: