We just discovered that the /rest/api/[version]/user/groups now requires ACT_AS_USER in order to be used. My guess is something similar. There was a similiar issue previously this week with /rest/api/3/user . Don’t know if there’s anyone at Atlassian available to dig into things.
Re: @daniel’s comment, we’ve kept the scope on our test app to only READ.
We can’t recreate problem. We’ve created a new default access user (not admin), but getting results back each time from within Connect app. Perhaps you can share more details that can help us reproduce… user and group access info, etc.
Is this happening across all instances you’ve tested against?
Do you have details about when this started happening?
What query parameters are you passing?
Can you test it with only project ID or key to see if that returns any results?
I think we also have one customer which might be facing this issue, though I think we are using the Version 2 endpoint. We got notified of this earlier this week (Tuesday), but cannot reproduce this in our instance. @nmansilla I’ll try to send you the affected instance in a DM. Not sure if this issue is still happening on that instance though, we’ll try to check with the customer next week.
Actually - not, it’s reproducible in majority, newly created instances but not on all of them (also we’ve already got a bunch of customers requests - complaining on broken picker (that uses mentioned endpoint under the hood) on their instances -> that is a result of a problems with this endpoint).
First complain was around 20th of September - few days after rising a request problem was gone (for that particular customer), then a long period of silence and now it’s started to pop-up for different customers.
Query, maxResults, showAvatar, project (tested on projectId and projectKey)
Done that - still the result is an empty list
What’s more - /rest/api/3/user/assignable/multiProjectSearch endpoint seems to work just fine for same use cases. And we encounter problems only when calling this endpoint through AP.request.
Just an idea - maybe You could try it on our test dev-instance (recently created) on which problem persists? It’s https://ziemniaki8.atlassian.net . Let me know if You will be able to check this or will need some explicit privileges to be granted.
We have seen the same issue with one customer but using the end pint /rest/api/3/user/search?query=$email
Where any query would return an empty result set. This normally works fine for all our customers, could it be related?