Thank you Kamil. Keep up the good work! We are looking forward to full feature-parity between GIT and HG across your product lines.

We are proud to announce that the long-awaited request for lines of code reporting was completed as part of the 4.3 FishEye release that is now available for download.

With the new Delta Lines of Code report you can track your repository activity, regardless of the type of SCM you use. You can get a repository overview, as well as a more detailed report that you can further customise by selecting committers, folder and date range.

For those who need even more insight into the revision data we improved EyeQL by:

• adding new capabilities
  • multi-value group-by
  • grouping by day, month, author
  • excluding merges
• speeding up query execution time

We would like to thank all our users who, by providing invaluable feedback, helped us shape this feature!

FishEye 4.3 Release Notes

Kamil Cichy,
FishEye & Crucible Software Engineer

Thanks Stan, I'm removing my vote, we don't need it any more we now use SonarQube instead as the reports out of there are comprehensive and include LOC.

Hello!
I am a new Product Manager for FishEye & Crucible and I just replied to the LoC for Git issue here. As I find this two issues really similar, let me please copy my recent comment here to update this issue as well.
Firstly I wanted to thank you all guys for interest, votes and informative discussion here. Your contribution to this issue is solid and that’s the spirit we love in our customers. I do understand that sometimes when you don’t see some feature released after years of discussion, it might seem like you’ve been ignored. So I do apologise for any negative experience you might had here, but the voice of the customers was never ignored here in Atlassian.
Lines of Code statistics is the most requested feature for FishEye, that’s why we’ll never put it off our list. Nevertheless, it’s a big effort for us, and we must be sure that we are addressing a big effort to solve really big problem. So I will appreciate if you guys can *share with me a little bit more context about challenges you are facing not having *LoC in FishEye.

• What problems would be solved having LoC stats in FishEye?
• What pain points do you experience without LoC statistics in FishEye and how this influences your workflow?
• If you will create list like “top 3 improvements that will make my FishEye experience much better” what will be #1?
  Thanks and really looking forward your feedback!

Stan Gladkov,
FishEye & Crucible PM.

Agree with S R. There appear to be quite a few votes for this issue as well.

It's been almost 2 full YEARS since this has been updated ... when is this going to be included?? It appears this story is not on any JIRA board??
@Matthew Watson [Atlassian] Any status you can provide?

It's been almost 2 YEARS since this was updated. Can we get a status update from Atlassian on this?

The attached diff hgfelog.py.diff fixes the problem and can handle both, old and new hg

Just evaluating FE/Jira, this is a disappointment. Same goes for Git. Well, of to write my own perl script...

Could the http://mercurial.selenic.com/wiki/ChurnExtension be of use for implementing this? It seems to be for the purpose of getting Lines of Code