Mikael Sandberg Community Champion

Okay, so I recreated this and it looks like you have to belong to a team in order to see remote repositories not owned by you. You learn something new every day...

You should be able to see remote repositories, as long as the hosting account is setup and works. I should have asked this before and you mentioned that you logged on to your Bitbucket account, but does that account show up on the left hand side in Sourcetree under Remote?

Just to rule out any issues with accessing the repository, have you tried cloning one of them, either by copying the git clone command and clone it from the command line or click on the Clone in Sourcetree button when you click on Clone in Bitbucket?

You could try and upgrade your PostgreSQL driver to the latest version and see if that does it, if not then you would have to upgrade to a supported version, see Supported platforms.

If you are new to Git I would recommend taking a look at Learn Git, it's a good starting point and gets you a good introduction to how to use Git.

Hi Marlene, And welcome to the Atlassian Community. Yes, you can share repositories between Bitbucket Cloud and Bitbucket Server. Have a look at Git Basics Working with Remotes it describes how you can do it. All you would have do to in Bitbucket is create the repository first.

Hi Michael, And welcome to the Atlassian Community. You should be able to treat the zip file the same way as any other files in a Git repository. All yo need is a repository, add the zip file to it and commit it.

Hi Wolfgang, And welcome to the Atlassian Community. The short answer is yes, the ownership of the content will be kept after the migration, as long as the username is kept the same. The only thing you do need to do is have the user log in again and assign them to the same group(s), if you are using local groups in…

I took a look at the branches that I see this on in our repositories, and it looks to be related to how those branches where created. I only see the reference to the repository on branches that was created in Sourcetree/terminal instead of within Bitbucket/Jira.

Hi Mehdi, And welcome to the Atlassian Community. So, if I understand your issue correctly, you are seeing a reference to the repository as part of the commit comment correct? Something like this: Merge branch 'source_branch' of ssh://bitbucket_URL/7999/project/repository.git into target_branch If that is the case, then…

Does the pop-up window say Git Credentials for Windows? If so, try and disable it and see if that helps. To disable it, run: git config --system --unset credential.helper You can also turn off the OpenSSH prompt by running: git config --global --add core.askpass "" 

You do not have to transfer the licenses to the new Server IDs, just apply the license key to the new server.

Hi Ali, And welcome to the Atlassian Community. BASE is the common ancestor before there where any changes to the file on either side. LOCAL is your side of the conflict, e.i. your changes made to the file. REMOTE is "theirs" side of the conflict, e.i. changes made on the branch you are merging from. BACKUP is what the…

Is there only one repository in the project? Maybe it is related to the defect I found were the first repository is not listed, SRCTREEWIN-8529. Did you try cloning the repository using the URL from Bitbucket?

See if the workaround mentioned in this thread works, https://community.atlassian.com/t5/Sourcetree-questions/How-do-you-get-SourceTree-to-show-Bitbucket-team-repos-on-New/qaq-p/631401

If you copy the URL in Bitbucket when you clone the repository and then paste it into Sourcetree, does it detect that it is a Git repository? What version of Sourcetree are you using?

A bit more information is needed in order to help you. When you say that the repository is not found, are you referring to that the search does not find it?

You can use memberOf as part of your user object filter to restrict the scope. Take a look at https://confluence.atlassian.com/crowd/restricting-ldap-scope-for-user-and-group-search-169118612.html. It is for Crowd, but you can use the filter the same way in Confluence. Note that it is not the number of users that you…

Okay, then check out this thread and see if the workarounds in it helps, https://community.atlassian.com/t5/Sourcetree-questions/Use-an-existing-account-window-is-blank/qaq-p/643924

And I forgot, welcome to the Atlassian Community!

I would recommend the get started guides that you can find in the documentation, those are really good starting point. Get Started with Jira Software Get started with Confluence Cloud Get started with Jira Service Desk

Hi @nina_bernard, And welcome to the Atlassian Community. See if the workarounds mentioned in this thread helps, https://community.atlassian.com/t5/Sourcetree-questions/Source-tree-doesn-t-work-on-windows-10/qaq-p/659483 Sourcetree relies on Internet Explorer to access https://id.atlassian.com/ to validate your account, so…

@Mark Moussa if you are referring to the new Agility template, then the board created when you create the project is not configurable. You have to use either the Scrum or Kanban template in order to be able to configure the board.

I am wondering if the embedded version is getting the app password from Sourcetree. You could try and generate a new app password and change your repository URL to this: https://[your_user_name]:[app_password]@bitbucket.org/[your_user_name]/[repo_name].git

The password errors could be from the Git Credential Manager for Windows, we have had issues with it and I always recommend not to install it, but it is not always that my developers follows my instructions...

Git has a default disposition of keeping data unless it’s explicitly thrown away. Prune will only remove the remote-tracking references, not the local branch itself. There is a request to have the feature to sync removed remote branches with local ones, SRCTREEWIN-8631. This one if for Windows, I could not find one for…

You can always download and install Git separately instead of using the embedded version. I have been running Git 2.17 for a while now with Sourcetree 2.5.5 without any issues.

2.5.5 is still being rolled out, Sourcetree moved to staged updates about a year and a half ago, have a look at this blog post about it. Only once the staged roll out reaches 100% will it be available to download from the website.

Jira keeps track of the issue key, so you can use either the old or the new key to get to the issue. If you are running Jira Server you could query the database to get a list of old and new keys, the change is stored in the changeitem table.

It is standard, so no configuration is needed.