Crucible - Add Content to Review - Nested branches


We are finally starting to use Crucible and have run into a question/issue. When adding content to a review (Add Content > Browse Changesets), it appears that we are unable to navigate to or choose a nested branch. For example, we have the following branch structure:


So, I was wondering if I was doing something wrong, or if it is not supported. If it is the latter, I am curious as to why (best practice, technical constraint, etc.).

We've tossed around the idea of making our branch structure flat (one level), but wanted to investigate further before changing our entire process.


1 answer

1 accepted

0 votes
Accepted answer
Lukasz Pater Atlassian Team Nov 04, 2012

Hi Eric,

While the list of branches in Browse Changesets is indeed flat, you can probably configure Crucible svn handling to use your current repository structure and get branches that are mapped to your directories with names like 'team1-project1' and 'team2-project3'.

To do that you'll have to set up symbolic rules for the svn repository, to tell Crucible what you consider a branch. You can see the details on this feature here: I believe your repo structure is similar to the 'Example from FishEye customer' one and you could use similar rules.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

447 views 6 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you