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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

historical commiters limit - Starter License

Norbert Rising Star Dec 04, 2017


In the artikel "restriction of starter license" there is following section:

  • Map Committers
    If your developers have not correctly configured their committer names for Git or Mercurial, they may have committed with multiple identities. It is then possible to remap these to correct the problem. See the knowledge base article, Git or Hg Repository exceeds number of allowed Committers

SVN is not mentioned here. Does this not work for SVN or is just not mentioned?
Because if not this is more like a bug for me....


1 answer

1 vote

Hi @Norbert,

This option only applies to Git and Mercurial repositories, which allow their committers history to be rewritten / remapped by following that link.

The other options from Restrictions on FishEye Starter Licenses apply to SVN repositories:

  • 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.


Felipe Kraemer

Norbert Rising Star Jan 08, 2018


The problem here is, that my svn project is quite old (~9 years)
So I have a lot of commiters but normally no more then 4 people work at the same time with the project..
Also because of some technical issues we have some Commiters with different names in the SVN...

so this also makes sense for SVN (I admit its rare case)


Nevertheless thanks for the answer
i solved the problem by limiting the history to 2 years. Its good enough for my use case.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events