Hello @StefanWienstrer ,
This can actually be related to the deprecation of Lenient URL path processing for OAuth 2.0 requests that we started rolling out on the 26th of February.
Due to this change OAuth 2.0-authenticated requests with URIs such as these will no longer return successful responses from Jira:
/%2Frest%2Fapi%2F3%2Fmyself
/rest/api/3/myself/
//rest//api//3//myself
For more details please see:
- https://developer.atlassian.com/changelog/#CHANGE-1320
- REST API: What is the correct scope required to create an issue in Jira (seems the same behavior reported in here)
Can you please check if this is the case or provide more details about the issue you are facing?