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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Exceeding committer limit with starter license due to temporary misconfigured git user configurations

We have a fisheye starter license for our small team of six developers. Since multiple of our developers had their git configuration incorrect for some time (i.e. their mail addresses were wrong causing the commits to appear to be from different users) we are now reaching Fisheye's limit of ten committers causing the initial indexing of the repository to stop. I was hoping that this could be solved using the user mappings, but apparently that does not change it.

Is there anything we can do aside from buying the next license level? Maybe manually change files in the repository to exchange the wrong git usernames with the correct ones?

Best regards,

Arne Bergmann

3 answers

1 accepted

1 vote
Answer accepted

There are a few solutions offered in Restrictions on FishEye Starter Licenses.
The two most practical are to set a start revision (very simple to do, but you'll miss part of the history in FishEye), and to map committers.
This is described in the Git or Hg Repository exceeds number of allowed Committers Knowledge Base article.
Although you can rewrite history, it's much simpler to use a .mailmap to map the incorrect old email addresses to the correct ones.

Please, provide a solution to map committers also for Subversion.

Its 2016 and no solution for this? We have 50+ developers in our Mercurial repository history but less that 10 active today.  Rewriting the history log is just out of the question. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

275 views 16 17
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