Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8934

REST API endpoint to delete customer account

XMLWordPrintable

    • 64

    • 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.

      Update December 2023

      Hey all, 

      We will be closing out this request as the public rest API endpoint https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-delete is here and works as expected to delete customer account users from a site.

      Feel free to reach out to me if there are any further questions or concerns.

      Cheers,
      Martin

       

      Problem Definition:

      There are endpoints to add user, remove user and all in Jira service desk but there is no endpoint to delete a customer account. It's a time-consuming task to manually delete 1000 users from the user management

      Suggested Solution:

      It will be great if there is an API endpoint to delete the customer account.

            [JSDCLOUD-8934] REST API endpoint to delete customer account

            Eric H added a comment -

            I believe this is supported now.

            The delete user endpoint is currently experimental but functional: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-delete

            And if you want to ensure you are deleting a portal-only customer account and not an Atlassian account, then search the user first.

            If you search for a user (e.g. via /rest/api/3/user or /rest/api/3/user/search) it returns an "accountType" property for each account. 

            If you see the entry has "accountType" equal to "customer", then you can delete that account by ID and it will delete the portal-only account.

            Eric H added a comment - I believe this is supported now. The delete user endpoint is currently experimental but functional: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-delete And if you want to ensure you are deleting a portal-only customer account and not an Atlassian account, then search the user first. If you search for a user (e.g. via /rest/api/3/user or /rest/api/3/user/search ) it returns an "accountType" property for each account.  If you see the entry has "accountType" equal to "customer", then you can delete that account by ID and it will delete the portal-only account.

            Abhishek Yadav added a comment -

            https://getsupport.atlassian.com/browse/PCS-165843

            Abhishek Yadav added a comment - https://getsupport.atlassian.com/browse/PCS-165843

            Abishek . added a comment -

            https://getsupport.atlassian.com/browse/JST-847451

            Abishek . added a comment - https://getsupport.atlassian.com/browse/JST-847451

            Andrew Daniels added a comment -

            https://getsupport.atlassian.com/browse/PCS-110914

            Andrew Daniels added a comment - https://getsupport.atlassian.com/browse/PCS-110914

            Robert Rodrigues added a comment -

            Please can we progress this? Being given the ability to delete a customer from a specific servicedeskID but not from the portal customers list is a problem for us.

            Robert Rodrigues added a comment - Please can we progress this? Being given the ability to delete a customer from a specific servicedeskID but not from the portal customers list is a problem for us.

            David Quiram added a comment -

            After a questionable import job of all of our Zendesk tickets, we ended up with hundreds of accounts added to our instance that we are unable to remove ourselves. The biggest problem this is causing for us is that in the Reporter drop down list, a person will have two entries. One entry for their current email address and the second one is for their old email address since we went through an domain change a few years back. 

            Should an agent create an issue for someone and select the wrong entry in the Reporter field, the user will never be able to see the issue or receive updates via email. 

            David Quiram added a comment - After a questionable import job of all of our Zendesk tickets, we ended up with hundreds of accounts added to our instance that we are unable to remove ourselves. The biggest problem this is causing for us is that in the Reporter drop down list, a person will have two entries. One entry for their current email address and the second one is for their old email address since we went through an domain change a few years back.  Should an agent create an issue for someone and select the wrong entry in the Reporter field, the user will never be able to see the issue or receive updates via email. 

            Paul Benati added a comment -

            Atlassian:

            This is a big deal for us.  We need customer account REST API endpoints for add, delete, and modify functions.  Thanks.

            -Paul Benati
              SVP, Global Operations

            Paul Benati added a comment - Atlassian: This is a big deal for us.  We need customer account REST API endpoints for add, delete, and modify functions.  Thanks. -Paul Benati   SVP, Global Operations

              a1217920d496 Ash Young
              mfaiz Mohamed Faiz (Inactive)
              Votes:
              52 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: