Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3239

Git: Support Lines of Code statistics and charts

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      FishEye does not currently support LoC stats or charts for Git repositories.

      Add in support for these.

      Note we had support in 2.3, but it was based on some code which worked really well for "linear" VCSs like SVN and CVS, but it was broken for DAG based commit graph systems like Git (and Mercurial: CRUC-4505). We are working on a better solution, but vote here to increase it's priority.

        1. image-2017-01-20-14-55-11-169.png
          image-2017-01-20-14-55-11-169.png
          266 kB
        2. screenshot-1.png
          screenshot-1.png
          6 kB
        3. screenshot-2.png
          screenshot-2.png
          27 kB
        4. Selection 1027x409 20141209085507-0800.png
          Selection 1027x409 20141209085507-0800.png
          146 kB

            [FE-3239] Git: Support Lines of Code statistics and charts

            We will schedule the upgrade immediately.  Thanks!!

            Brian Cummings added a comment - We will schedule the upgrade immediately.  Thanks!!

            Wonderful! thanks a lot Atlassian and Crucible/Fisheye team!

            Jean-Claude Passy added a comment - Wonderful! thanks a lot Atlassian and Crucible/Fisheye team!

            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

             

            Kamil Cichy (Inactive) added a comment - 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  

            The line charts, and commit activity reports available in Fisheye/SVN.
            Commit activity reports available in GIT, but line charts missing in GIT.
            Line charts help see the growth of the repositories by projects by lines of code.

            Here are the sample line charts for fisheye/svn:

            The similar line chart doesn't exists for fisheye/git.
            Having this will help us to show the line growth by project.

            Thanks,
            Trinadha

            Trinadha Goddu added a comment - The line charts, and commit activity reports available in Fisheye/SVN. Commit activity reports available in GIT, but line charts missing in GIT. Line charts help see the growth of the repositories by projects by lines of code. Here are the sample line charts for fisheye/svn: The similar line chart doesn't exists for fisheye/git. Having this will help us to show the line growth by project. Thanks, Trinadha

            What problems would be solved having LoC stats in FishEye?
            • Lets us know how quickly our application is growing
            • Gives us a very high level view into the complexity of our application
            • Is a cool stat to throw at senior leaders.
            What pain points do you experience without LoC statistics in FishEye and how this influences your workflow?
            • We don’t really use the stat other as it’s so arbitrary and using it as a metric actually promotes poor coding practices and reporting.
            If you will create list like “top 3 improvements that will make my FishEye experience much better” what will be #1?
            • Ability to Mention someone and have it work like it does in Confluence / Jira with email notifications and messaging notifications.
            • Ability to tie into SONAR so during code reviews we could also see SONAR code violations.
            • Better integration with JIRA
            • Prevent issues from transitioning to certain statuses if they have no code review but check-ins/ or open code reviews.
            • Search ability in JQL i.e. find all stories which have /do not have code reviews open, closed recently etc.

            Brian Cummings added a comment - What problems would be solved having LoC stats in FishEye? • Lets us know how quickly our application is growing • Gives us a very high level view into the complexity of our application • Is a cool stat to throw at senior leaders. What pain points do you experience without LoC statistics in FishEye and how this influences your workflow? • We don’t really use the stat other as it’s so arbitrary and using it as a metric actually promotes poor coding practices and reporting. If you will create list like “top 3 improvements that will make my FishEye experience much better” what will be #1? • Ability to Mention someone and have it work like it does in Confluence / Jira with email notifications and messaging notifications. • Ability to tie into SONAR so during code reviews we could also see SONAR code violations. • Better integration with JIRA • Prevent issues from transitioning to certain statuses if they have no code review but check-ins/ or open code reviews. • Search ability in JQL i.e. find all stories which have /do not have code reviews open, closed recently etc.

            Kingsquare added a comment -

            Stan,

            just to come back to this as we did leave a comment 3 years ago: we have since moved on and ditched fecru entirely. Partly due to the feature disparity between SVN and GIT (at that time) and partly due to tooling provided outside of the fisheye ecosystem elsewhere...

            So just from us: we might as well drop our '+1' as we've moved on a long time ago and are not coming back to fisheye/crucible...

            Kingsquare added a comment - Stan, just to come back to this as we did leave a comment 3 years ago: we have since moved on and ditched fecru entirely. Partly due to the feature disparity between SVN and GIT (at that time) and partly due to tooling provided outside of the fisheye ecosystem elsewhere... So just from us: we might as well drop our '+1' as we've moved on a long time ago and are not coming back to fisheye/crucible...

            david.grierson1, thanks a lot. Yes, I'm aware of that comment and totally agree that case is strong and valid. More arguments like that we can identify - the easier decisions can be made. So I will really appreciate other users sharing their LoC-related problems here to give us more context.
            Cheers.

            Stan Gladkov (Inactive) added a comment - david.grierson1 , thanks a lot. Yes, I'm aware of that comment and totally agree that case is strong and valid. More arguments like that we can identify - the easier decisions can be made. So I will really appreciate other users sharing their LoC-related problems here to give us more context. Cheers.

            Stan - if you'd read the comment just two before the one you posted you'll see a great example of the kind of perfectly valid business case for providing LoC stats.

            David Grierson added a comment - Stan - if you'd read the comment just two before the one you posted you'll see a great example of the kind of perfectly valid business case for providing LoC stats.

            Hello!
            I am a new Product Manager for FishEye & Crucible. 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.

            Stan Gladkov (Inactive) added a comment - Hello! I am a new Product Manager for FishEye & Crucible. 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.

            ibaca added a comment -

            Perhaps atlassian products have this really high quality thanks to ignore this kind of issues . It's obvious that they spend much more time in Stash (now Bitbucket server) than fisheye in the last years. We migrated from fisheye to stash after we realized this situation instead of trying to fight with the reality. I also empathize with this situation because I have experienced this same situation/obsession by some clients and managers which try to force the developer team to do a task which is not totally justified especially compared with the effort required to be done. And when you try to discuss some alternative solution, they just get more obsessed than the issue must be done as they like.

            ibaca added a comment - Perhaps atlassian products have this really high quality thanks to ignore this kind of issues . It's obvious that they spend much more time in Stash (now Bitbucket server) than fisheye in the last years. We migrated from fisheye to stash after we realized this situation instead of trying to fight with the reality. I also empathize with this situation because I have experienced this same situation/obsession by some clients and managers which try to force the developer team to do a task which is not totally justified especially compared with the effort required to be done. And when you try to discuss some alternative solution, they just get more obsessed than the issue must be done as they like.

              Unassigned Unassigned
              mwatson@atlassian.com mwatson
              Votes:
              541 Vote for this issue
              Watchers:
              270 Start watching this issue

                Created:
                Updated:
                Resolved: