We are using OAuth 2.0 (3LO) app to make API calls to Jira Cloud.
We are using the API to read issues and also to write issues.
Using the token created with the oauth flow, we are able to read the issues but creation of the issues is failing with 401.
This was working before and we started observing this 401 behavior recently.
Is there anything changed from Jira SIde?.
Below is the authorization url used
https://auth.atlassian.com/authorize
?audience=api.atlassian.com
&client_id=PUesxfvPz8GruyEQtXyJr7JigCoBRyAW
&scope=offline_access%20read:jira-work%20write:jira-work
&redirect_uri=https://url/callback
&state=cmVkaXJlY3RVcmw9aHR0cDovL2xvY2FsaG9zdDo0NTAwL3Rlc3RtYW5hZ2VyXy9vYXV0aENhbGxiYWNrLG5vbmNlPTUyZDNiYjU4LWU0OTUtNDRjMi1iMzhmLTJlYjI5ODgyZDE5Myxjb25uZWN0b3JJZD05ZDYwZTRmZC0wYjAwLTAwMDAtMDE1Ni0wYjQ2OGM1NTlmM2YsY29ubmVjdG9yVHlwZT1KaXJhQ2xvdWRPQXV0aCxhY3Rpb249Q3JlYXRlRGVmZWN0LHByb2plY3RJZD0zZmEzMjhlYS0wMTAwLTAwMDAtNTYwZi0wYjQ2NzI0ZTJiYTE
&response_type=code
&prompt=consent