We are adding a new tool to our platform: Bitbucket!
Bitbucket is a great git for "End-To-End Visibility & Automation Across the Entire Development Process". Because you asked for it, our Bitbucket integration allows you to import pull requests to better track development activities across all - or selected - projects in one place. Combined with our JIRA integration this allows you to have full visibility on development priorities.
Neat eh? How does it work?
Development items are automatically prioritized based on due dates and recommended actions. Issues (from JIRA, Trello or ClickUp) and pull requests can also be cross-referenced (auto-linking) and aggregated to further optimize your priority inbox.
#security we do NOT fetch your code. Keypup doesn't need to access your code in order to evaluate priorities on development items. Be assured that if we ever needed to access your code in the future in order to deliver a new feature we would make it an opt-in feature. See section below "What data do we collect?".
Also important: we NEVER update data automatically in third-party applications. Updates in third-party applications are ONLY performed under your control via remote actions. See section below "What remote actions can you perform?".
What data do we collect?
Our Bitbucket integration fetches the following entities:
- Comments: used for display in the dashboard
- Commits: used to detect links between issues and pull requests
- Pull requests: used for display on the dashboard. Pull requests can reference issues via auto-linking (title or description) and nest them in the Priority Inbox.
- Pull request approvals: used to evaluate the review/approval status of pull requests and recommended actions.
- Pull request build statuses: used to evaluate the readiness of pull requests and recommended actions.
What remote actions can you perform?
Our Bitbucket integration allows you to perform the following remote actions from the dashboard:
- Link pull requests and issues: pull requests and issues can be linked to each other directly from the Priority inbox using the link icon. In order to link items we update the description of the parent pull request and add a closes: https://issue-url.domain auto-linking keyword at the bottom of it.
- Merge pull requests: approved pull requests with a green build - if any - and a mergeable status can be merged directly from the Priority Inbox and Review & Merge board.
- Quick reply on items: it is possible to comment on a pull request from the Priority inbox.
How often do we refresh data?
Updates from Bitbucket are received in real-time via webhooks.
The only exception to this are "request changes" events by pull request reviewers, which have to be long polled every 20 minutes. We have filled a bug with Atlassian and it is currently being addressed by their team.
If for any reason we are unable to setup real-time updates on Bitbucket - e.g. the user who connected Bitbucket has no admin access on a given project - then we revert to long polling data every 20 minutes.
Whenever possible we recommend connecting Bitbucket projects as an admin to get the best experience.
How to link issues to pull requests?
Simply use the URL or key (e.g. PROJ-123 for JIRA) of your issue in your pull request title, description, or in one of your commit messages with a closing keyword. This works for JIRA, Trello and ClickUp.
With JIRA you can also include the issue key (e.g. PROJ-123) in your branch name.
E.g. linking via pull request title
[PROJ-123] My PR title
E.g. linking via pull request description
This is my PR description.
# Via issue Key
# Via issue URL
E.g. linking via commit message
Fixes signup button - closes PROJ-123
Fixes signup button - closes https://doecop.atlassian.net/browse/PROJ-123
E.g. linking a JIRA issue via pull request branch