Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crucible/Fisheye: not all included directories being shown

My "AP" repository's branch/directory structure is as follows

/branches/..other stuff..

I'm interested in submissions on trunk and on "some" subbranches under '/branches/release/' and everything under /branches/reviews/. When I configured the Includes/Excludes path for this repository, the following was specified

Under Includes, it was left blank while under Excludes the following branches were defined:


This leaves only the latest release branch /branches/release/14.x/ but when I try and view the changelog via, it will display /branches and /branches/release but nothing under /branches/release/...

If I look under the 'Commit Graph' tab (i.e., I can see submissions made to /branches/release/14.x/xxxxx and from there I can select "Go to changeset" and see the deltas/diffs of the files that were submitted. For each file, the entire directory path is shown and each subdirectory is individually selectable. (i.e. but nothing happens if I select these subdirectories.

Note: The repo was setup with "Store Diff Info" enabled.


1 answer

Under Excludes (but not includes) you can use the anti-glob wildcards (I think that's what they are called)  Try adding


instead of just


It may actually be getting an error on the path without the wildcards which may be blocking the indexing.

One other thing to check out.  Look to see if you're running into licensing issues.  We hit this a month or so ago.  It seems that there were more users who had historically committed to our svn repo than we were licensed for.  (Yes it looks at the commit names as unique current users regardless of how old the checkin is).

Because the license levels were exceeded the indexing never completed and thus branches never appeared in the viewer.


Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

133 views 0 8
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you