Jira Plugin: OAuth error on API calls to Jira

Description

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:
https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement-connect
https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide

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`

QA Test Steps

Authentication

  • Connect

  • Disconnect

  • 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)

Attach comment

  • Working as expected

  • Permissions are respected

Transitions

  • Transitions work

  • Transitions Permissions are respected

Activity

Show:
Dylan Haussermann
July 19, 2019, 1:44 AM

Tested on 5.13.1-rc1

The functionality is working. We still should confirm that existing users will not need to reconnect.

Dylan Haussermann
July 19, 2019, 2:37 PM

Tested on 5.12.5-rc1 - The functionality is working as expected on 5.12 as well

Dylan Haussermann
July 19, 2019, 3:27 PM

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,

Slim BHIRI
September 16, 2019, 12:16 PM

Having same issue on 5.12

Done

Mana

4

Assignee

Christopher Poile

QA Assignee

Dylan Haussermann

Reporter

Michael Kochell

Epic Link

None

Mattermost Team

Integrations

Sprint

None

Labels

None

QA Testing Areas

Plugins

GitHub Issue

None

Components

None

Severity

None
Configure