Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,189
Community Members
 
Community Events
177
Community Groups

Workspaces are "blank" when selecting remote repos in Sourcetree

Edited

When adding a remote repository in Sourcetree from a Bitbucket account the dropdown to select which workspace has a line for each workspace and you can select them but the lines are blank.

OkBis

The same with the Light theme
rRB96

I've tried reinstalling Sourcetree, including wiping user settings/config, to no avail.

These are the workspaces that I have on Bitbucket and are definitely the 2 things im choosing from in the dropdown.
uJU0u

Also posted on Stackoverflow here 

6 answers

Happening to me too.
Wondering if anyone have a solutions for this..

I can confirm i suffer from the same behaviorScreenshot 2022-03-14 104842.pngior. 

For my Bitbucket account the primary workspace shows up in SourceTree remote repositories. It is the additional workspaces that are blank.

@Andy Liddle Maybe you need a Jira account? In any case, the issue is closd now and the fix is implemented in Sourcetree 3.4.11 version.

Yeah I have a jira account.  but it does looks like it's finally fixed in 3.4.11

This has been happening for quite a while and Atlassian has done nothing.

Think there are 3 or 4 related issues already raised. 

 

here's one of them https://jira.atlassian.com/browse/

Any solution yet?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events