Bitbucket
J
Jason Counihan
## Bitbucket: Configurable defaults for repository and source branch
### Problem
Creating a Bitbucket branch from a ClickUp task requires users to manually select the repository and source branch each time, even when the task’s Space is linked to only one repository.
These repeated selections add unnecessary steps and increase the risk of creating a branch in the wrong repository or from the wrong source branch. For teams migrating from Jira, where these defaults were configurable, this is a workflow regression.
### Requested functionality
*
Default repository per Space:
Allow admins to configure a default repository. Automatically select it when only one repository is linked.*
Default source branch per repository:
Allow admins to specify the source branch used when creating new branches.*
Override when needed:
Prepopulate both fields while allowing users to change them before creating a branch.### Expected outcome
Users can create a branch from a task without re-entering predictable settings, reducing clicks and preventing avoidable mistakes.
### Acceptance criteria
* A Space with one linked repository automatically preselects that repository.
* A Space with multiple linked repositories uses its configured default, if one exists.
* Selecting a repository prepopulates its configured source branch.
* Users can override either selection before creating the branch.
* If a configured default is unavailable or inaccessible, ClickUp prompts the user to select a valid option rather than silently substituting another value.
Log In