I know that /rest/api/3/expression/eval it is deprecated from some time, but suddenly it stopped working for previous scopes:
read:jira-work, read:jira-user
It returns now: 401 (Unauthorized)
After I switched to new API /rest/api/3/expression/evaluate, it started to work
I just wanted to warn you
1 Like
@Floating-electron we are seeing that any call to the old api are failing this way now. Switching to the new path only works as long as all the result entries are few enough to fit within one request and you weren’t using page fetching. If you had been relying on totalCount and using startsAt to handle multiple pages of results you’ll still be broken. The new api makes you walk through all of those pages sequentially using the nextPageToken - which can add quite a bit of latency and might lead to problems if you are trying to get them done in a single lambda call.