Uploaded image for project: 'Identity'
  1. Identity
  2. ID-248

Unable to update username using JIRA REST API in Cloud

XMLWordPrintable

      Summary
      Unable to update username using JIRA REST API in Cloud

      Steps to reproduce

      • Send https:// {instance_URL}

        /rest/api/2/user?username=

        {username that you want to modify}
      • JSON: { "name": "test" }
      • It will produce the error like below: 
        {
    "errorMessages": [
        "This user can not be renamed because that operation is unsupported by the underlying user directory or JIRA is acting as a Crowd Server."
    ],
    "errors": {}
}

      Expected Behaviour
      Based on this documentation https://docs.atlassian.com/jira/REST/ondemand/#d2e5367 , we should be able to modify the username in Cloud.

      Affects Versions

      • 6.5-OD-08-001

            [ID-248] Unable to update username using JIRA REST API in Cloud

            Michael Andreacchio made changes -
            Workflow Original: reviewflow [ 914498 ] New: JAC Bug Workflow v3 [ 3258072 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Adarsh added a comment -

            marion.knopp -  This issue is linked to  https://jira.atlassian.com/browse/JRACLOUD-66936 and the issue is resolved. Also, please be aware of major changes coming to Jira REST API's. You can find more about it here - https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/

             

            Adarsh added a comment - marion.knopp -  This issue is linked to   https://jira.atlassian.com/browse/JRACLOUD-66936  and the issue is resolved. Also, please be aware of major changes coming to Jira REST API's. You can find more about it here - https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/  

            Marion Knopp added a comment -

            asridhara  Since this is resolved as 'tracked elsewhere' - could you add the information where it is tracked?

            Marion Knopp added a comment - asridhara   Since this is resolved as 'tracked elsewhere' - could you add the information where it is tracked?
            Adarsh made changes -
            Resolution New: Tracked Elsewhere [ 15 ]
            Status Original: Verified [ 10005 ] New: Resolved [ 5 ]
            Eric S (Inactive) made changes -
            Component/s New: API authentication [ 48703 ]
            Component/s Original: User management [ 33497 ]
            Adarsh made changes -
            Link New: This issue is duplicated by JRACLOUD-66936 [ JRACLOUD-66936 ]
            Rusty (Matt) (Inactive) made changes -
            Status Original: Open [ 1 ] New: Verified [ 10005 ]
            vkharisma made changes -
            Link New: This issue is related to JRACLOUD-47275 [ JRACLOUD-47275 ]
            Shawn C made changes -
            Link New: This issue is related to JRA-47275 [ JRA-47275 ]

            Samiran Ghosh added a comment -

            This issue exists for JIRA cloud, should have worked as per documentation https://docs.atlassian.com/jira/REST/ondemand/#api/2/user-updateUser

            Samiran Ghosh added a comment - This issue exists for JIRA cloud, should have worked as per documentation https://docs.atlassian.com/jira/REST/ondemand/#api/2/user-updateUser

              Unassigned Unassigned
              afajri Aulia Fajri (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: