Problem Definition

In Bitbucket Server 4.1.3, and JIRA 6x/7x, the JIRA Dev Panel displayed commits for the parent and for the forks. Post upgrade to 4.11.1, we find that this is no longer the behaviour due to bug BSERV-8748. The JIRA Dev Panel now only shows the commits for the parent, and ONLY unique commits for the fork.

Problem Impact

This change to BitBucket affects us by limiting visibility into code deployments.

In our workflow with "legacy" clients, separate forks exist for the DEV, STAGING, and PROD environments. Before this behavior change, we could see the status of each commit on a per-environment basis directly in the Jira ticket.

Now that only the first unique commit is shown, the only way for us to know which commits have been merged to which environments is to download the repos and manually grep through the git logs for each individual commit hash.

While this is still workable, this task has gone from taking a couple seconds per ticket to a couple minutes, and is now more error-prone.

Suggested Solution

Perhaps it makes sense to stop the list at a certain (user-configurable) number of forks, or only X forks with the most recent activity, and put the rest behind a "show more" button in the JIRA UI.