our svn repository structure is like below :
which means one repository has multiple modules, and each module has its one branch and tag folders.
The question is if in fisheye I create one repository for one module, it is quite difficult to maintain, because we have more than 20 modules, and it will be more and more later.
And now I create one repository for all modules based on the SVN repository ROOT.
But the issue is when add content to review, the add branch function is not working as expected, it will create diff based on the whole repository for all modules.
So how can I only add one repository for all modules and still benefit from add branch function when add contents to review?
Thanks for your reply. If we create repository based on modules, it will be so many repositories, is it possible to group repositories by project. which means when I create a review, and select a project, only repositories under that project will be displayed. currently as long as a user has permission, when add content to a review it will see all repositories which he has read permission, it is quite noisy to see other repositories which not related with the project due to so many repositories.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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