Summary:

We would like the development panel to have bi-directional linking between Bitbucket Cloud and Jira issues. This is in the interest to make best use of the Development dashboard.

Steps to reproduce:

1. Create a Jira issue of type Story (say AB-123 be the Jira issue key)
2. Create a branch and some commits without mentioning the Jira issue key AB-123 (i.e. no link established yet between AB-123 and bitbucket/git just yet - observe that the Jira issue still shows "Create branch" as the only available content in its Development panel (Initial state))
3. Create a PR for that branch and mention AB-123 in the PR "Description" field with the intention to link it by doing so
4. Optional: Approve/Merge the PR

Observation:

A) In the created PR Description field the string "AB-123" is displayed as hyperlink and upon click navigates to the Jira issue with issuekey AB-123 - that is expected behaviour and is OK from my point of view; and it gives the impression that the Jira issue has been linked successfully.
B) When navigating to Jira issue AB-123, the Development panel does not show any information about the PR, the branch, the commits, the deployment status etc.; instead it shows the initial state link "Create branch" as the only available content - This is not the expected behaviour from my point of view.

Request:

At least there is an inconsistency in linking the Jira issue, as in point A) above it seems like the Jira issue was successfully linked but in point B) above it becomes apparent that this link is only one way. The expected intuitive behaviour (from my point of view) would be for the linking to be consistent, i.e. both ways.