Integrations
BitBucket
HacknPlan integrates with Bitbucket to attach commits to work items automatically.
When a push event is received, commit messages are scanned for item references using the configured prefix (default: hnp-, for example hnp-5).
Create the integration
Open Administration -> Integrations in your project and select New in the Bitbucket panel.
You must provide:
- Bitbucket account email
- API token
Create an API token
API tokens are user-based tokens that replace the legacy App passwords. They offer scoped permissions and don't require two-step verification.
To create an API token in Atlassian:
- Select your profile avatar in the upper-right corner of the top navigation bar.
- Select Account settings.
- From the Atlassian Account page, select the Security tab on the top navigation bar.
- Select Create and manage API tokens.
- Select Create API token with scopes.
- Give the API token a name (e.g. "HacknPlan") and an optional expiry date, then select Next.
- Select Bitbucket as the app and select Next.
- Select the following scopes (permissions) and select Next:
- Repositories — Read (
read:repository:bitbucket) - Workspaces — Read (
read:workspace:bitbucket) - Account — Read (
read:account) - Webhooks — Read (
read:webhook:bitbucket), Write (write:webhook:bitbucket), and Delete (delete:webhook:bitbucket)
- Repositories — Read (
- Review your token and select Create token.
- Copy the generated API token immediately.
Complete setup
After credentials are validated, choose the repository and click Connect.
Optional setting:
- Process existing commits: scans repository history for pre-existing
hnp-references.
Test the integration
Push a commit that references a valid item, for example:
Integration test for task hnp-1
If processing succeeds, the commit appears in the work item Source Code tab with a link to Bitbucket.