Would this still be an option to be implemented? I know it is still in the gathering interest phase - but it would be a great and valuable update if it can be shared on how high this is on that list as i can imagine there is a ton of more stuff on that list. 

Workaround:

1. Go to the user admin section
2. Open the browser console → Network → clean it up
3. Deactivate a user
4. Copy the "deactivate" request as a CURL (bash worked for me, cmd - did not)
5. Paste into a bash .sh file where replace user IDs (two places) with "$1", example

'.../users/<accountId>/deactivate'
replace with
'.../users/'"$1"'/deactivate'

1. Create another .sh file where call the first one with account IDs as the first parameter, i.e.

./deactivate.sh 12345678910
...

1. Remember that Bash .sh file should use LF as the end of line, if you are on Windows
2. Run the main bash file ./caller.sh

That's it.

If watching this add your votes also to the following, perhaps then it may get traction to be implemented

Currently votes are divided across multiple aged tickets, if the votes were consolidated, then the pressure is on to get this implemented

JRACLOUD-37294 Allow set active/inactive via REST API - Create and track feature requests for Atlassian products.

• created 03/Mar/2014
• 216 votes

JRACLOUD-44801 JIRA API disabling users - Create and track feature requests for Atlassian products. 

• created 14/Aug/2015 
• 396 votes

JRACLOUD-70752 Provide public REST APIs for user management as in server - Create and track feature requests for Atlassian products.

• created 11/Oct/2018
• 28 votes

ID-7711 REST API to activate/deactivate users - Create and track feature requests for Atlassian products.

• created 16/Jun/2020
• 87 votes

Please, rescue your org admins from the hell of manual and repetitive activities!

252f2e9b44bf We are actively working on it. When released it will work for customers on our new user management experience. https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592

Any timeline for the suspend\restore API to be released to the public?  

We are actively working on a public API to suspend users.

We'd like to get feedback before making it public.

If you're interested in directly influencing the experience, please email me to set up a time for a 1 hour conversation.

Thanks.  jrautenberg@atlassian.com

Hi 39985cb03ae7, I would like to talk to you more about your use case. Are you able to send me an email at sscorse@atlassian.com? 

I'd like to discuss what APIs would enable this use case for you.

Thanks!

Our use case for needing this feature is that we are moving from another system to Jira and we want to migrate only issues/bugs related to releases of packages for our internal stack.  We eventually want to shut down the previous system.  We would like to retain all the previous users at the company who filed the bugs & PR's and add them as real users so we can add them to the issue.  In order to do this we need to create a bunch users and add them to the issue and then disable their Jira access. 

1.  We can create all the users via the rest api but cannot turn on has site access, therefore we cannot add the user as the assignee or creator of the ticket.
2. Manually enabling 5000 users by hand is not an option.
3. We did not use an IDP until recently because all our internal and external stack had no requirement for one until 6 months ago (we work on mostly desktop software, not web based).
4. Sure, Atlassian access would give us the ability to do this but then we would have to enter 5,000 ex-employees into the software and then disable them.  This is equally as annoying as #2.

2015ae912494 same as Andrey, the endpoint is not applicable to unmanaged accounts and my customer