The Jira API calls are returning a `400 Bad Request` because of the Jira userkey deprecation for the GDPR migration. Here are some Jira docs explaining the deprecation:
Here is the error that we receive when opening the `Create Issue` modal or the `Channel Subscriptions` modal:
Here is the error we receive when trying to `/jira connect`:
`invalid JWT: no user data`
Mapped user's name displays correctly in Jira when making changes to issues and comments
Disconnect and re-connect as a different user
Create issue (All issue types)
Working as expected
Permissions are respected
Transitions Permissions are respected
Tested on 5.13.1-rc1
The functionality is working. We still should confirm that existing users will not need to reconnect.
Tested on 5.12.5-rc1 - The functionality is working as expected on 5.12 as well
Tested and passed. The plugin changes return the plugin to a functional state without the need to re-connect.
No changes needed to release testing. This task can be closed,
Having same issue on 5.12