We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.83
    • 10.80
    • REST API
    • None
    • 1
    • Severity 3 - Minor
    • Breakers - Usher 8

      Issue Summary

      There is an issue when using a PATCH request (REST API 2.0) on a user. The problem is that when a user is updated via patch the user loses their API token.

      Reproduces against https://alignsupport.jiraalign.com

      Steps to Reproduce

      1. I used my own account for this purpose. userid is 661675
      2. My API token prior to it being removed was
        Mpxg6+4Y(U<`ynh[z_:Dips`Y&l5BeGOJId)RwXs
      3. I ran the following API call to change the start date for my user account:
        curl --request PATCH --url https://alignsupport.jiraalign.com/rest/align/api/2/Users/661675 --header 'authorization: Bearer Mpxg6+4Y(U&lt;`ynh[z_:Dips`Y&l5BeGOJId)RwXs' --header 'content-type: application/json' --data '[ { "op":"replace", "path": "/userStartDate", "value": "2020-04-01T00:00:00Z" } ]'
        

      Expected Results

      User info is updated, but, API token should remain.

      Actual Results

      I checked my user account's profile after making the API change, and noticed that the API token had disappeared:

      Workaround

      The affected user will need to re-generate a new API token to continue using API 2.0 against Jira Align

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Bug Bug
              • Resolution: Fixed
              • Icon: Low Low
              • 10.83
              • 10.80
              • REST API
              • None
              • 1
              • Severity 3 - Minor
              • Breakers - Usher 8

                Issue Summary

                There is an issue when using a PATCH request (REST API 2.0) on a user. The problem is that when a user is updated via patch the user loses their API token.

                Reproduces against https://alignsupport.jiraalign.com

                Steps to Reproduce

                1. I used my own account for this purpose. userid is 661675
                2. My API token prior to it being removed was
                  Mpxg6+4Y(U<`ynh[z_:Dips`Y&l5BeGOJId)RwXs
                3. I ran the following API call to change the start date for my user account:
                  curl --request PATCH --url https://alignsupport.jiraalign.com/rest/align/api/2/Users/661675 --header 'authorization: Bearer Mpxg6+4Y(U&lt;`ynh[z_:Dips`Y&l5BeGOJId)RwXs' --header 'content-type: application/json' --data '[ { "op":"replace", "path": "/userStartDate", "value": "2020-04-01T00:00:00Z" } ]'
                  

                Expected Results

                User info is updated, but, API token should remain.

                Actual Results

                I checked my user account's profile after making the API change, and noticed that the API token had disappeared:

                Workaround

                The affected user will need to re-generate a new API token to continue using API 2.0 against Jira Align

                        kforeman@atlassian.com Kyle Foreman
                        kbaxley Kent Baxley
                        Affected customers:
                        0 This affects my team
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            kforeman@atlassian.com Kyle Foreman
                            kbaxley Kent Baxley
                            Affected customers:
                            0 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: