Develop and production branches missing from Bitbucket branch menu, but commits are still visible

Question

We noticed that our develop and production branches are no longer showing in our Bitbucket repository Branch Menu. As far as we know, no one manually deleted these branches.

The commits from those branches still appear to be available in the commit history, and we are still able to generate builds, so it does not look like the underlying commits/artifacts are completely gone. However, the branch refs themselves seem to be missing or not visible in Bitbucket Menu.

Could Altassian/Community have a look and let us know what causing it :

* What could cause long-lived branches like develop and production to disappear from Bitbucket without a user manually deleting them?
* If commits are still visible and builds can still be generated, does that indicate the branch refs are hidden, renamed, detached, or affected by some repository/CI configuration?
* Is there a way to confirm whether the branches were deleted, hidden, renamed, pruned, or affected by automation?

Any guidance on where to look in Bitbucket Cloud / Atlassian settings, audit logs, branch permissions, repository activity, or CI/build configuration would be appreciated.

Ben · Answer

Hi @AGeorge

You're likely not seeing these, as they are not active branches. An active branch is a branch which is different from the main branch (ie it has commits that do not exist in the main branch).

When you load the branches view, the selected branches that will display are Active branches, you can click the dropdown menu and select All branches which should show you these missing branches that you've mentioned.

Cheers!

- Ben (Bitbucket Cloud Support)

Ajay _view26_ · Answer

Hi @AGeorge

Welcome to the community!

Sometimes Bitbucket's internal ref cache gets out of sync. If your commits are still there and your CI pipelines are pulling fine, the branch HEAD refs likely still exist at the Git level but aren't being surfaced in the UI. You can verify this by running

git ls-remote origin

from your local machine and checking if `refs/heads/develop` and `refs/heads/production` show up. If they do, the data is intact — it's a UI-side caching issue.

If `git ls-remote` shows the refs are truly gone, you can recreate them easily since the commits are still in the git:

git checkout -b develop origin/develop (or from the last known commit hash)

git push origin develop

Same for production. Since your commit history is intact, you won't lose anything — you're just re-attaching a label to a commit that already exists.