Bitbucket

Bitbucket rarely arrives on its own. It comes with Jira and Confluence, chosen as a set by a company that wanted its planning, documentation and source in one vendor.

For a property group with an internal development team, that consolidation is usually deliberate — one licence conversation, one permission model, one place for IT to administer.

Connecting Bitbucket extends that consistency to the assistant. Pull requests, repository history and pipeline results become answerable in the same conversation as the Jira ticket that prompted them, provided both are connected. As with the rest of this category, the audience is your technical team.

If your company does not build software, none of this applies and there is no hidden hospitality angle. Bitbucket is here because Atlassian shops exist inside property groups, and those teams deserve the assistant to work with their stack rather than around it.

Once Bitbucket is connected, ProhostAI works with your repositories, pull requests and pipelines in plain language.

Read

• Search repositories Find code and history across the repositories you can access. "Did the last pipeline on the booking repo pass?"
• Check pull requests and pipelines See what is open, what is blocked and whether builds passed.

Create & update

• Comment on pull requests Leave a note on a PR without switching tools.
• Update issues Keep repository issues current as work moves.

Bitbucket connects through Atlassian OAuth, so ProhostAI never sees your password.

1. Open ProhostAI and go to Settings → Connections.
2. Search for Bitbucket and select Connect.
3. Sign in to Bitbucket and approve the permissions.
4. Ask about open pull requests to confirm it works.

• Access follows the connected Atlassian account’s workspace and repository permissions.
• Connecting Jira as well is worth it — the ticket and the branch usually belong to the same question.
• This serves your engineering team rather than property operations.