• 191
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Currently it appears the /rest/api/2/user (PUT) API doesn't provide facility to set users active or inactive, or perhaps the request representation doesn't include how this is done. Currently the API works fine for the following fields:

      {
          "name": "eddie",
          "emailAddress": "eddie@atlassian.com",
          "displayName": "Eddie of Atlassian"
      }
      

      Can something like "Active": 1 or "Active": true be made available for this API as well to set the Activate or de-activate a user?

            [AX-1215] Allow set active/inactive via REST API

            Hey Team,

             

            Is there any update on this request ?

            Anshuman Bakshi added a comment - Hey Team,   Is there any update on this request ?

            Any progress on that? I need to deactivate a user via REST as well using /rest/api/3

            Guilherme Moura added a comment - Any progress on that? I need to deactivate a user via REST as well using /rest/api/3

            Nicolas PR added a comment - - edited

            So, just to clarify, there's no way to deactivate a user via the REST API for Jira or Access (cloud) ???

            Nicolas PR added a comment - - edited So, just to clarify, there's no way to deactivate a user via the REST API for Jira or Access (cloud) ???

            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

            Mark J Cunningham added a comment - 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

            Hi how close is a working API for this now?

            Would expect something like a POST to

            https://<instance>.atlassian.net/rest/api/3/user?accountId=AccID

            Typical Headers

            {     "active": false }

             

            or 

            {     "active": true }

             

            to deactivate or activate the user

            Mark J Cunningham added a comment - Hi how close is a working API for this now? Would expect something like a POST to https://<instance>.atlassian.net/rest/api/3/user?accountId= AccID Typical Headers {     "active": false }   or  {     "active": true }   to deactivate or activate the user

            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

             

            cc:

            de8395d2e3cf 

            11e546011bce 

            369ea363d9e2 

            Josh Rautenberg (Inactive) added a comment - 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   cc: de8395d2e3cf   11e546011bce   369ea363d9e2  

            +1

            Dylan Richards added a comment - +1

            I've found that PATCH does work to make the user record visible and active.
            /isLocked is set to -1 if the user record is not visible or active.

            Add following to update isLocked to 0 and you should then see the record in the people list.

            [

             

            {     "value": “0”,     "path": "/isLocked",     "op": "replace",   }

            ]

            Mark Northcott added a comment - I've found that PATCH does work to make the user record visible and active. /isLocked is set to -1 if the user record is not visible or active. Add following to update isLocked to 0 and you should then see the record in the people list. [   {     "value": “0”,     "path": "/isLocked",     "op": "replace",   } ]

            Any updates on this?

            Hector Villafuerte added a comment - Any updates on this?

            Hi Team,

            It would be very helpful to have this feature enabled. It would save a lot of time of Jira admins as right now inactivation of users needs to be done manually what becomes problematic if you have hundreds of users to modify.

            Damian Karp added a comment - Hi Team, It would be very helpful to have this feature enabled. It would save a lot of time of Jira admins as right now inactivation of users needs to be done manually what becomes problematic if you have hundreds of users to modify.

              Unassigned Unassigned
              takindele Taiwo Akindele (Inactive)
              Votes:
              279 Vote for this issue
              Watchers:
              158 Start watching this issue

                Created:
                Updated: