FishEye and Crucible: License limit reached, indexing stopped

[Deleted user]

2 weeks ago I got the starter pack

1 week  ago started throwing License limit reached, indexing stopped

Other atlassian products are working w/o a hitch some do have a higher license count.

[Caterina Curti · Accepted solution]

Hi Hal,

You can find the current restrictions on the Fisheye and Crucible starter license on the Restrictions on FishEye Starter Licenses page.

These are the current ones:

• 5 FishEye users
• 5 repositories
• 10 historic committers per repository

The page also explains how to Reconfigure your repository to keep using Fisheye. If the repositories are Git or Mercurial, you can also consider rewriting the history of the repositories to reduce the number of committers per repository.

Thanks, Caterina - Atlassian 

[dead mike]

i too am getting this error and don't really like the 10 committer limit. i've taken over a software company and there have been more than 10 cimmitters but will only be ONE fisheye user and one repo. so is it indexing or is it stopping? what are our choices now? we only need the committer level upped. never had anything like this show up under the trial license NOR ANYWAY TO EVALUATE THIS CONDITION TO THE LICENSE SINCE THERE IS _NO_ APPARENT EXPOSURE OF HOW MANY COMMITTERS FISHEYE FOUND.

[Caterina Curti]

Hi @dead mike,

If the repository contains more than 10 committers, the indexing will stop.

It is very likely that the evaluation license used did not have this limitation as it was issued for a higher number of users.

Is this repository a Git or Mercurial one? If that's the case and you are ok in losing the history of the committers, you can follow the instructions on the Git or Hg Repository exceeds number of allowed committers page to map to committers to a single one or a reduced number. Note: the history of the repository itself will not be rewritten. Only the committers will be updated.

The logs will also contain the list of the committers identified by Fisheye is a log line that can be identified by the following text:

Committer limit exceeded - committer list

[dead mike]

SVN repo and no answer except to accept a 110x price increase to merely LIST NAMES but not provide any functional differences. the committers, how ever many there are i have no idea, are part of the enduring history of the company, but certainly not applicable to the current real world and real space situation where we don't have that many people accessing it still... sad arbitrary and capricious limit solely designed to not provide any more real world capabilities above reporting, but simply a sales decision to get 110x more money for a product we might use once a month... sad you are even here in texas with us, but such a sad policy that seems un-texan in nature.

not acceptable to us for such a disused product.