Bitbucket Integration Problem
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
We received the following communication from Atlassian re: Bitbucket
[!NOTE]
Atlassian is phasing out Connect, the legacy framework used to build apps for Bitbucket Cloud, and moving to Forge as its primary app development platform. Support for Connect in Bitbucket Cloud ends on January 31, 2027.
It doesn't look like there is a Forge option for the Sentry Bitbucket integration. What is the path forward?
Expected Result
Continued support for Bitbucket
Actual Result
No forward path has been disclosed.
Product Area
Settings - Integrations
Link
No response
DSN
elemental-machines
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the existing Bitbucket integration and the Atlassian Connect-to-Forge timeline; done requires an agreed path for continued Bitbucket support.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100