Issue Summary

When both an OAuth integration and an App Link exist between Bitbucket and Jira Cloud, configuring the integration to support workflow triggers and eliminate duplicate development information causes the "Create Branch from Jira" functionality to disappear. This is because the recommended configuration requires disabling "View Development Tool Data" on the App Link, which also removes the Create Branch action. There is currently no configuration that allows workflow triggers, no duplicate dev info, and Create Branch functionality to coexist.

Steps to Reproduce

1. Set up both an OAuth integration and an App Link between Bitbucket and the same Jira Cloud site.

1. On the OAuth integration in Bitbucket, enable "Development information" to ensure workflow triggers fire.

1. In Jira Cloud, navigate to Settings → Products → Application links → "..." menu next to the Bitbucket link → Smart Commits → toggle off "View Development Tool Data" to remove duplicate development information.

1. Confirm the Smart Commits toggle itself remains on.

1. Navigate to a Jira issue that is linked to a Bitbucket repository and attempt to create a branch from the development panel.

Expected Results

The "Create Branch" action should remain available in the Jira issue development panel, even when the integration is configured to support workflow triggers without duplicate development information.

Actual Results

The "Create Branch from Jira" action disappears from the development panel. This occurs because the Create Branch functionality is provided via the App Link pull path, which is disabled when "View Development Tool Data" is toggled off. Since Bitbucket's internal filter suppresses push-based events through the App Link when an OAuth integration also exists, there is no configuration that preserves all three capabilities (workflow triggers, no duplicates, and Create Branch).

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available