Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Fisheye Subversion repository exceeding license limit of starter license, due to number of committer

I inherited a legacy SVN (Subversion) repository which I would like to index in Fisheye and I would like it to be indexed from the first commit and all the 49000 commits.

I know how to add user mappings so a Subversion commiter is mapped to a Fisheye username and I have done so for all the Subversion committers I can find by browsing the repository history in Tortoise SVN client. 

My user mappings are quite many but even after going through the commit history and adding every committer I can find to the mapping table, I am still unable to complete the indexing of this repository... it always says license is exceeded and stops indexing.

How can I make sure this repository can be indexed into Fisheye without hitting the license barrier ?

Please advice,



2 answers

Hi @Felipe Kraemer,

Thanks for your response. 

You mentioned generating a 30 day trial license and import the repository using that license. 

What happens to the repository when I apply the starter license after the import / indexing is finished? Will the repository stop working ?


Hello @Pall Bjornsson,

In that case, you will start facing the exact same problem you're currently facing.

Fisheye will identify that a Starter license is configured and will apply the restrictions that license has and, as the repository will have more than 10 committers in its history, indexing will stop. You will still be able to see everything that got indexed that far, but you won't be able to index new changesets.



Hi @Felipe Kraemer,

Hmmm.... I actually wonder what will happen after the indexing completes.

I did start the test by creating an evaluation license and started indexing the SVN repository. After the first phase is done, I browsed the repository and see that there are over 70 committers.

However, the user mappings seem to be working, as the committing users are only two, myself and the other FishEye user all the rest of the committers is mapped to.

So now, what will FishEye starter license be looking at when it starts this repository? Will it be the total number of committers stated in the browse repository summary, or will it be the total number of FishEye users said to be the FishEye users/committers, which are only two ?


Hi @Pall Bjornsson,

Fisheye considers the total number of committers stated in the browse repository summary, i.e., ~70 committers you have mentioned, that is why indexing will stop whenever the Starter license is configured again after the indexing finishes.



0 votes

Hi @Pall Bjornsson,

I am afraid you won't be able to accomplish that while using a Starter license.

As mentioned at Restrictions on FishEye Starter Licenses, your options are:

  • Generate a 30-day evaluation license, selecting a license that allows more users than the Starter license.
  • Upgrade your existing Starter license, which willl remove the user limit.
  • Reconfigure your repository, by either:
    • Changing your repository definition so as to look at a subset of your repository, reducing the indexing scope and the number of users involved.
    • Excluding parts of your repository that are not really relevant. Committers that are active only in these areas will not appear in Fisheye and will not be included in the committer count.
    • Set a specific revision to start indexing from. All commits prior to this starting point will be ignored by Fisheye, so the committers who performed those commits won't be included in the committer count.

The 4th option mentioned there, Map Committers, applies only for Git and Mercurial repositories, and this should be done at Git / Mercurial repository level, not at Fisheye.


Felipe Kraemer

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

How we use Jira Service Management for our recruitment process! - Part 2

It is never about setting up a process and being done with it. Rather, the focus should always be on optimizing it for the best outcomes. Thus, we didn’t stop at setting up JSM for our recruitment pr...

187 views 0 5
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