Issue Summary

According to Link Bitbucket With Jira, we encourage users to configure both an Application Link and OAuth credential to integrate Jira Software Cloud and Bitbucket server.

When doing this, you get 2 separate tabs in the Development panel of each connection which duplicates the data since they are from the same Bitbucket server.

Steps to Reproduce

1. Create an Application Link between your Jira Software Cloud and Bitbucket server
2. Create an OAuth credential connection between your Jira Software Cloud and Bitbucket server
3. Send any development data to Jira from the Bitbucket server (commit, pull request, etc...)

Expected Results

There should be 1 Bitbucket server displayed.

Actual Results

We can see 2 tabs representing the same Bitbucket server but duplicated.

Also, each respective tab only displays data from the moment the connection was created.

Workarounds

Whilst we work on a better solution, there are two workarounds for this issue.

Workaround 1: Remove the OAuth credentials

If you don't need any of the extra functionality provided by the OAuth connection, you can remove the OAuth credentials in Bitbucket so Jira Cloud gets all the development information it needs from the Application Link.

Workaround 2: Make a one-way Application Link

If you want the extra functionality provided by the OAuth connection, you can change the Application Link so it's one-way.

This workaround maintains all functionality of both connections but has one cosmetic side-effect in Jira Cloud. The dev info panel will show a yellow warning indicator indicating that it can't get development information from Bitbucket:

Clicking on the the warning indicator shows this message:

Development information will still flow to Jira Cloud via the OAuth connection, so this warning can be ignored.

Steps to make a one-way Application Link:

• Disable the outbound Application Link in Jira Cloud
  • Settings -> Products -> Application links -> (Bitbucket DC link) -> ... menu -> Edit
  • For the "Outgoing" direction, select "Disabled"
  • Click "Save changes"
  • The Application Link will show as "Config error"
• Disable the inbound application link in Bitbucket
  • Administration -> Application links -> (Jira Cloud link) -> Edit (pencil icon)
  • For the "Incoming" direction, select "Disabled"
  • The application link should show as "Connected" with a direction of "Outgoing"
  • In Jira Cloud application links, the Bitbucket link should now show as "Connected" (you may need to refresh the page)