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

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?

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 :/

Couple of years on and this seems like it's still an issue.

We have users in three countries and can't find a clean way to be able to route tickets based on a users location, surely this is a fundamental now.  We can't even see how to map it from Okta, is this just not an attribute we can map over?

Agree with the above. It is crucial to be able to see a user's location when managing multiple offices/countries.

Echo comments above. Our organization too has users in many locations and so location is one of the essential pieces of information. Please enable mapping this user field for automatic user provisioning.

Hello,

We serve many global organizations and will now need to write custom scripts to handle this functionality that could otherwise be handled via user provisioning.

The long term costs of maintaining such scripts can be quite high.

I believe that ideally any arbitrary attributes should be able to be set via user provisioning.

Thanks,
Ian

I agree with the earlier comments that this is a higher priority need than a Sev3. With over 22 offices, I need to route support tickets based on customer's location to the correct desktop support team.

Having the customer's location in the ticket is an essential piece of information for any Service Desk/Support Team.

I agree with JP Elrod, this is a higher priority.

This bug is a high priority for us as a Jira Service Desk customer. IT agents can't determine where an employee who submits a ticket works without first going to another directory service to figure it out because of this bug. Please fix it.