Is anyone running Plane with Bitbucket Data Center in production?

We’d like to replace Jira and Confluence while keeping Bitbucket as our Git server. Any feedback on stability, missing features, or workflow limitations?

  • Can a Plane issue automatically create a Bitbucket branch?
  • Can commit messages like PLANE-123 link back to the issue?
  • Can a merged PR automatically move the issue to “Done”?
  • Can developers navigate from a Plane issue to the PR in one click?
  • Does authentication work cleanly through Keycloak/OIDC?

:slight_smile: Thanks everyone!

Thanks for the detailed questions. We’re actually working on a Bitbucket integration right now, currently in testing and expected to go live sometime mid July.
To answer your specific questions

  1. Auto-create a Bitbucket branch from a Plane issue - There’s no branch creation capability currently, but noted as a feature request.
  2. Commit messages linking back to the issue - Not fully supported in the way you’re describing. Plane picks up issue identifiers (e.g. PROJ-123) from the PR title and description, not from individual commit messages. So referencing the issue in your PR title or description is what triggers the link, not the commit itself. I’ve shared this with this team as an enhancement request.
  3. Merged PR moving the issue to Done - Supported. When a PR is merged, Plane automatically moves the linked issue to your configured “Done” state.
  4. One-click navigation from issue to PR - Supported. When you reference an issue in a PR, Plane adds the PR as a clickable link directly on the issue.
  5. Authentication via Keycloak/OIDC - Plane supports OIDC-based SSO, so Keycloak should work fine, this isn’t Bitbucket-specific.

Let us know if you have any other questions as you evaluate.

Thank you so much, Danica, for the detailed information. I can’t wait to see what the integration looks like.

Regarding point 2, it might be worth taking a look at how Jira detects issue keys from Bitbucket commit messages as well as PR titles and descriptions. That workflow has proven to be quite convenient in our day-to-day development.

That said, if the first release includes the capabilities you described, it will already be a very promising starting point, and we’ll definitely perform a deeper evaluation from there.

Have a great day!