API 2.0 - When running a GET against a user the teams are not ordered so a Patch does not have consistent behavior

Issue Summary

When a customer does a GET request on /users/

, the "teams" array keeps coming back in random order. They would like it to come back in the same order consistently.

This is due to the customer adding teams via API and using path /teams/- in PATCH requests

Steps to Reproduce

1) Add one or more teams via Jira Align API using the path /teams/- in PATCH requests like so:

[
    {
        "op": "add",
        "path": "/teams/-",
        "value": {
		"teamId":1807
	}
    }
]

2) Run a GET call via Jira Align API to the following user endpoint:

https://xxxxxxx.jiraalign.com/rest/align/api/2/users/{userid}

Expected Results

Team order in the array comes back consistently in the same order whenever a GET call is used against a user id

Actual Results

The the "teams" array keeps coming back in random order.

Workaround

The workaround (and possibly safer approach) is to get the user's current list of teams, parse the array and POST the user with a new array with the allowed teams only.