Feature Request: Contributor Statistics (BB-4787)

Issue #4307 resolved
Kevin VanGelder
created an issue

Had an idea recently. Bitbucket should add a tab to each repo with Contributor Statistics. Number of lines of code, lines of code overwritten (usually either mistakes/bugs or inefficient), percentage of lines kept vs lines overwritten, number of commits, etc. Obviously this would be mostly informational as repo's are constantly in flux, but I want to know if my boss, my co-workers, or I wrote the most code in a given project.

Just thought it would be really cool, and not too difficult for Atlassian to add...

Official response

  • Matt Ryall staff

    Hi all,

    Thanks for all the votes and recent comments on this issue. It's clear from all the enthusiastic discussions here that people are looking to get more visibility into the way their teams work, in order to work smarter and better. This is something we want to help you do with Bitbucket.

    However, this ticket has grown into a monster over the years. Looking at the comments above, many people want wildly different things, or even very specific requests that wouldn't be widely applicable.

    The original request, for basic author-level contribution stats, is now well covered by the Awesome Charts for Bitbucket Cloud add-on, which is freely available to all Bitbucket users. You can install it as an individual, and immediately get statistics on any repository you have access to. I've just tried it out now, and as a development manager myself, can see that this meets many of the needs for a quick report about top contributors on a repository.

    The team behind this add-on at StiltSoft is also a great partner for Atlassian, and supports dozens of extensions across our product suite for thousands of customers. They have been responsive in fixing the timezone issue highlighted above in this thread, and I'm sure will help with any further requests to expand contributor reporting in Bitbucket.

    Based on this, we now consider this ticket resolved. There is now an easy way to meet the original requester's needs. There are also many many ways to get statistics from your Git or Mercurial repo for the more advanced, more specific use cases described above (LOC counts, etc).

    To the point that this is an add-on rather than a core feature - Bitbucket and Atlassian as a whole spends a huge amount of time enabling and encouraging our ecosystem to fill feature gaps in our products. This is because despite having large teams on Bitbucket and our other products, we still can't do everything. Not even close. So rather than rebuilding what StiltSoft has already done a good job on, we're going to focus our efforts elsewhere in the product.

    At the moment, we're busy improving Bitbucket Cloud in the following areas:

    • pull requests
    • code search
    • pipelines & deployments
    • design and user experience.

    Based on your interest in this issue, I'm sure you will have some ideas of how we can make these better, especially around how we can provide high level visibility/statistics on how your teams are working together.

    So we'd love to see tickets submitted with ways we can help you understand more about how your team works in these areas. Maybe you want to know the lag time between PR creation and merge. Or deployment frequency to production. We'll be looking for useful statistics like these we can add as part of these feature improvements, and would love your feedback on what would help your team the most.

    Thanks again for your continued use and passionate enthusiasm for Bitbucket. It's this energy that keeps us going, trying to build the world's best code collaboration tool for your teams.

    Cheers,
    Matt and the Bitbucket team

Comments (594)

  1. fcabouat

    Just had the same idea. Not only to compare with co-workers, but also for one-man projects, to be able to track day-to-day productivity.

    So, +1

  2. ADesrosiers

    I agree, this would be really useful for determining how much developers contribute to a project and how active the project is at a given time. I hope they will add this feature in the future.

  3. Ville Saalo

    Yep, this would be great. :) In the past I have used StatSVN to create visual statistics of SVN repositories, so this could take ideas from there. I especially like the Developer stats there, and the Repo Heatmap is also a nice tool to play with. :)

  4. Sven Ginka

    Kevin VanGelder , so all the "+1"s are useless so far. From my point of view statistics is a very important thing to know where to put the focus. Bitbucket is a nice place to host projects, however others offer statistics. I'll put an eye on others and will see if it is worth a move over to another provider.

  5. Samuel Haddad

    It would also be nice if the user could choose to make statistics public even if you contributed to a private repo. You could show you are an active developer even though you might be working on a private project.

  6. Justen Stepka

    Official update:

    At this time we do not have an estimate for when this feature will be implemented. Our focus for the short to medium term, will be to provide SSO and better user management with our OnDemand JIRA and Confluence products. I would estimate that the SSO integration and bi-directional oAuth integration between Bitbucket / JIRA / Confluence / Bamboo will take us into 2014, at which time we will re-evaluate this decision.

    Cheers, Justen -- Bitbucket product manager

  7. Gabriel Gohier-Roy

    This is the only thing missing about BitBucket that has made me think more than once about switching to GitHub. I love the free private repos, but I just wish it had all those bells and whistles, as well as the social aspects that make GitHub so much fun to use! I think this would inevitably bring more traffic to the service.

  8. Chesley Brown

    Can people just "Vote" for the issue instead of just adding "+1" comments? I imagine they are more focused on up voted feature requests than looking for "+1" comments...

  9. Lucas Cavalcante

    I agree with your Chesley. Some people receive e-mail updates when an issue is commented. Maybe we should look for more constructing comments and use the Vote feature for "+1"

  10. Doug Freed

    If it helps provide some design ideas for the Bitbucket team, a friend of mine reverse-engineered the soup that is the Javascript that generates the Github stats graphs and using the data from their API, made his own graphs as SVGs:

    https://github.com/akerl/githubchart/

    See this repo for the code that parses out the data points for making the charts:

    https://github.com/akerl/githubstats/

    It'd probably be worthwhile to use the same mathematical algorithm if you're going to use a similar graph approach, so that us Bitbucket users can compare ourselves to Github users to show them how much better we are :P

  11. Konstantinos Psychas

    For one more time: *If you don't have anything useful to say about the issue, do NOT post!*

    Vote for the issue at the top. This is currently the highest voted issue by the way so if you can't find where to vote, it won't make a difference. There are 200+ people that receive email updates about it and don't want to see +1 every day. I'm wasting their time too right now...

  12. Konstantinos Psychas

    I asked because I didn't notice any increase in the number of votes the last 3 hours. I guess you voted long before you wrote +1. '+1' is not a vote. Votes are on the top of the page. The issue by the way is characterized as minor but I hope they will work on it soon

  13. Alberto Perales Beltrán

    # 2323: Create a way to group repositories / projects by tags, folders or labels (BB-1086) -> 777 votes, created 2010-12-06 and major priority

    # 4307: Feature Request: Contributor Statistics (BB-4787) -> 711 votes, created 2012-07-05 and minor priority

    This way of prioritizing the requests of the community, it makes little sense to me.

    And please everyone who commented with a "+1" is more effective vote, although it seems that they are not taking into account

    https://twitter.com/marcusbertrand/status/319968661601406976

  14. Alex Corn

    @Afner Perales It makes sense to me. Categorizing repos creates better organization and makes the site easier to use. It gets downright bulky when you have about 20 repos to manage. Contributor statistics are a convenience that would be nice to have, but at the end of the day they're a low priority.

  15. abhishekrm

    Great idea! This is supposed to work only on public profiles obviously. Even if a user has private repos, the overall amount of commits he does, and how active is he on bitbucket really, should be present on the profile page. This comes in handy when we need to check contribution done by others on a project or when we showcase our profile somewhere else. It'd be nice to have this feature. The feature could be something similar to that present in Github already!​

  16. Ricardo Fiorani

    Thanks to the bunch of as*les that instead of voting it up on the right side menu, comments "+1" in here and keeps spamming my email... now I'll have to unwatch this and never know if this feature will be available soon. Thank you.

  17. asl97

    @Ricardo Fiorani calling everyone asles isn't the solution, you just become part of the problem, everyone that is watching get a email about you calling them asles which is no different than those +1 but those +1 bump the issue so it's a good thing while you calling everyone as*les is just plain old rude

    be part of the solution by setting up rules in your email to move them to a different folder and automatically mark them as read or just delete them using the rules and not part be of the problem

  18. PaulBGD

    The fact that this hasn't been added yet after all these years saddens me. It reminds me of a few other things that bitbucket has mostly ignored over the years.

  19. Jochen Reinschlüssel

    I am currently looking into all git-related stuff and after all reduced my selection to bitbucket as well as github. Graphs are a thing thats really missing on bitbucket, but I'd like to keep this because of private repos - so please: give it a chance an add graphs!

  20. zac morris

    These statistics would be meaningless. They would measure how much typing was done, not functionality delivered. It's the code you don't have to write because of good design that provides the most value to a project, not how much typing you did.

  21. Michael Hamilton

    Zac: You can also see how many lines were removed (indicating efficient re-factoring) and how many original lines remain unchanged since they were written (indicating stability).

    But largely yeah, it's not a useful metric for functionality delivered. It is a good measurement of code stability and project scale. More code is more work to maintain, and while you can quibble about the difference between a 400 line and a 1200 line project, it is useful to see a 1000 line vs a 10,000 vs a 50,000 project grow.

  22. balazsh

    I'm only 3-5 days watching this issue, but i'm already annoyed with people 'crying' about this. Please notice, that this issue is not a bug, neither a major issue. It's a simple proposal / enchancment - which is related only to statistics...

    I haven't seen any project going ahead just because you have statistics on contributors. But already experienced the opposite: tons of hour wasted on statistics, meetings...

    So PLEASE push simply the VOTE button, and DON'T LEAVE messages with no really content - like +1 Thank you.

  23. Alex Gray

    @eq_pe That is pretty harsh and unproductive. There are workarounds to get most, if not all of this information. See above comments, like "You could clone the repo and use gitinspector (or some similar tool) to examine it.", which has worked fine for me. Or you could roll your own code via BitBucket's API's. My sarcasm radar may not be working, but our company has used BitBucket with almost no issues at all.

  24. Rolando Lora

    Guys, don't fight, remember we remain here not only for this feature request but to be part of the issue 4307 community. Watching sporadic +1s and people getting angry for it. We'll love BitBucket ;)

  25. eq_pe

    @Alex Gray I must stand by my original assertion. Their complete disregard to user requests is unacceptable. I've come to this thread from the 2 factor authentication which is even lower on the list of requests, and from technical stand point requires trivial amount of time to implement.

    The fact that they don't bother implementing these features speaks volumes about their management and individual drives of their engineers.

    They promised progress on these features and never delivered, and did not communicate any updates.

  26. Ross Smith

    @Alexander Riggs: Exactly. I've given up hope that BB wants to help customers in any capacity. With their customer service I cannot in good faith recommend BB to any colleagues. In the future I'll turn to GitHub, whose customer service is solid and whose involvement with the community is quite visible.

  27. Alberto Perales Beltrán

    I'm sure the BB team can do their job very well, but I can't understand that no action is taken to listen to the demands of your user community. However many users love this company, among whom I include myself. I even bought the t-shirt commemorating the milestone of reaching the figure of 1M users. But the perception I have of BB today, is very different :(

  28. Graham TerMarsch

    @Igor Stepanov / @Balazs Nadasdi - Is very disappointing. Open feature request that's over 2yrs old with 1200+ votes, and there's no indication of any progress on it from Atlassian.

    As for those who say "Oh, just go run git-stats yourself, its easy"... that's what makes this even more disappointing... considering that there already is a tool to gather/collect much of that info, its not like Atlassian has to build all of this from scratch, so why haven't they added it in?

    Its damn tempting to set up a second remote so that I can not only push changes up to BitBucket, but then also push a copy of it all over to GitHub/GitLab so that I can get some easy reports out of it. But gee... if I do that, then WhyTF are we keeping a copy of it at BitBucket. :o

  29. David Miraut

    In view of the Community's interest in this feature, perhaps Atlassian developers could consider to add it only in paid plans. So, its develoment and the server overhead could be amortized :-?

  30. Graham TerMarsch

    Lets see... "Issues -> Open -> Order by Votes, descending"... screen capture top five Issues.

    Gee... this is not only the top voted Open issue for BitBucket, but is well ahead of anything not in the top three (by number of votes). Almost 3x as many votes as the #5 most voted issue.

    Atlassian... ya think this tells ya something about how useful/important a feature your Users think it is? And hey... if you're not going to do anything with the top-voted issues, be honest about it and just turn voting off, or close the ticket as "won't fix". Not providing any feedback just leaves us to think you simply do not care about your Users and paying customers.

    bitbucket-top-voted-issues.png

  31. MustaphaF

    Of course Atlassian is aware of that feature...

    It's just a matter of business plan,

    such feature is probably available on Git Essentials product or Jira, bit bucket doesn't aim the same goal... and that would make bitucket a competitor of other products of the same company... which is not great for business right ?

    But, it'could be at least a paying option for that. I think a lot of people would buy it.

  32. Gav Allan

    Coming from a company that used GH to one that uses BitBucket feels like a really backwards step due to the lack of these kind of features.

    If we even had a definitive answer about what was happening here then that would help. Just tell us what plan there is.

    I find it impossible to believe that Atlassian is unaware of this thread so their silence speaks volumes. </rant>

  33. Ross Smith

    I'm not holding out any hope for anything I want to ever be incorporated into bitbucket. On the New Features page, they list only 3 features in the web interface completed for the entire year of 2014.

    Good thing bitbucket isn't the only game in town (although they sure operate like they are).

  34. Lukas Welte

    It's just ridiculous that there isn't even an answer by Atlasssian to a 2,5 year old issue that is by far the most voted one.

    Even if their strategy would not include this issue, it would be a relief to actually know what is in their mind.

  35. Graham TerMarsch

    @durazell ... that's part of why I'm pissed about not having this feature. I am working on a paid/private project.

    Makes me wonder WhyTF I'm letting my own management continue to pay for Atlassian OnDemand... my entire team gripes about it weekly, and with (lack of) answers like we're getting here from Atlassian its not like I have anything that I can take back to my team (or my management) to explain why we're continuing to pay for these services.

  36. Raimana Lowgreen

    Most voted feature request, almost 3 years old and not a single answer from Atlassian (not even a negative one)... Seriously, can someone from Atlassian say something!?!?

    And don't tell me to use git-stats or similar - of course I could but - is your car dealer telling you to install your own tachometer or listen to your engine noise to figure out the RPM...

  37. Anonymous

    How bloody useless is Atlasssian if they can't even just come up with SOMETHING? Just a stupid graph would be a start.

    Yet NOTHING. unbelievable.

  38. DennisKvdM

    Hi there,

    First of all, I'd like to apologize for the lack of responses from Atlassian on this issue. We acknowledge that this has been unanswered for a while and we will be giving more updates on a regular basis. Believe it or not, we have been following this as well as all other top-voted issues, and have had numerous discussions about it. It's currently not on our roadmap, not because we never intend to do it, but simply because we've got some other big projects in the works ahead of this one.

    Managing priorities is always a balancing act. Certainly user votes do carry a lot of weight, which is part of the reason we're working on #516 (another highly-voted issue), for example. Rest assured that we are paying attention, and if/when we start working on this feature those watching this issue will be the first to know! If you have any additional questions, please respond to this issue.

    Cheers,

    Dennis Kromhout van der Meer, Bitbucket PM

  39. PepeAmpere

    I knew once comics is added in discussion it encourage BB to answer ^^. Btw If would be on BB place, I wouldnt work on it, too. It is out of the profile of the Altassian services/products.

  40. Tri Nguyen

    Please do not comment a "+1". Use the vote feature instead. Commenting here spams everyone who's subscribed to the issue for more serious comments/ updates. I know I'm sorta breaking the rule by saying this, but I felt like it was needed to be said.

  41. asl97

    to all who keep complaining about +1, seriously, how hard is it to add a filter to your email client to ether mark mail from this issue as read or move it to a special folder or auto-delete it as soon as it enter the inbox?

    if we get one hundred plus +1 per day, then the developers of bitbucket might get it too and stop ignoring this issue.

  42. Cristian Beskid

    @asl97 some are viewing the issues in the browser, not in any mail client and the "+1" are only obfuscating any useful comments users might have to add. voting for the issue instead of spamming the thread might actually help solving issues much faster. i personally would expect at least that much logical reasoning from other developers

  43. Lochlan McIntosh

    Talking about spamming the thread is another form of spamming the thread. (Including this post.) The ad hominem implication that the +1ers are not using "logical reasoning" isn't helpful either.

    Just scroll past the comments you don't want to read. We already know this feature isn't even on the BB roadmap, so I think we can safely assume that there's no fix coming in the foreseeable future. /unsubscribe

  44. Gav Allan

    Atlassian finally responded with "we might". They are however working on another high voted issue (487 votes, this one has 1539) that was initially raised in February 2009.

    This request was raised in July 2012. So all we have to do is wait another three and a half years for this to be worked on.

    I'm going to stop watching this thread, there's no point, this isn't going to happen within a time-scale that's useful for me.

  45. PepeAmpere

    @Gav Allan "this one has 1539"... which payed Altassian something like 0 $ total for developing it. Altassian is not a charity and this is not voting competition. Once it doesnt fit their portfolio (and it really doesnt) and once they would make it for free, why the hell they should care about it? So pls keep you acid comments in your mouth.

  46. Gav Allan

    @PepeAmpere We pay Atlassian a decent monthly fee for BitBucket usage as we are a large organisation, so no charity implications there. We are actually a fairly major customer of their various products. My comment was more exasperation than acidic, unlike yours.

    My comment was more about how Atlassian, on this topic, seemed to be coming across as not listening to their customers, which as you say they have every right to do. I personally don't think it's in their interests.

    Interesting that you think these tools don't fit their portfolio, I would have to disagree. Developer productivity is surely one of the key tenets of what Atlassian are all about. It certainly appears in their competitors portfolio.

  47. Daniel Eloff

    GitHub API offers contributor stats. I signed up for a paid plan based mostly on that. Judging by other comments here, this is a heavily requested feature and something a lot of people (including myself) would pay for. Why Atlassian doesn't see this as higher priority is strange to me.

  48. Rikard Herlitz

    2.5 years later, nothing....the slow development together with slow response times of the servers are making us do the switch to github, even if their pricing model doesnt fit us as well as bitbuckets

  49. Sandesh Damkondwar

    I was watching this issue from long. I guess, It's pointless to comment here now. Put the '-1' & announce that you are shifting to github to shame BitBucket team for not listening to paid users and organizations.

    BTW looks like that manager was on big vacation trip(he might be very slow also if he was not there on vacation) and other than Sam nobody else was there to look at those important issues from last two and half years.

  50. Andrey Rudenko

    @PepeAmpere, you should understand just one main thing, that all business is based on clients/customers. If you create a functionality for features voting then probably you want to know what features the community want you to add. So when you ask "who votes" = "customer", I would answer yes, since it's not my opinion, it's obvious thing based on functionality that Atlassian offers us (its cliens) to use.

  51. Raimana Lowgreen

    As expected @PepeAmpere, you missed the point, i.e. no customers = no successful business. It's not about whether or not I agree with you - you are free to say/think otherwise...

    Surely feature requests with votes aren't just there for people to flame.

    Implementing/not having a feature that is popular is - almost certainly - going to differentiate product ABC to product XYZ. Once your application have solid foundations, the votes count (free users or not) can be an indicator of what "nice to have" features is likely to make the most impact and of course there are other factors - again you are free to deny that it has its weight in the balance.

  52. PepeAmpere
    • @Andrey Rudenko "who votes" = "customer" was question for raimana, i asked YOU three different questions which you ignored. I was interested in magic dependency between some voting and change of profit. I was asking for it because I do not believe you and I would not risk my money to prove it. As same as Altassian does.
    • @Raimana Lowgreen You seem to be some oracle. You know what I missed, you know how my bussiness is going. Good luck with your "nice to have" approach. I hope you create great products with such approach (link to them is welcome!).

    "Nice to have" approach in practice: http://ulozto.sk/live/x9uwGvKw/jak-si-pejsek-s-kocickou-delali-dort-avi

  53. Andrey Rudenko

    @PepeAmpere, Well sorry, I was thinking it's a kind of rhetoric questions, let me answer it then. :)

    vote = $, really? - Not everything is done for money, some things are done for attracting new people to the community. Concurency is important here. ;)

    How you know who votes, just btw? - Simply, user is a customer/potential customer. If the community is opened then all users are customers. Every body are equal here, and if someone is commiting to free repo, that doen't mean he is the person without rights, agree?

    How you know "more votes = more $"? - Probably a duplicate of first question.

  54. Herman Groenenboom

    @Andrey Rudenko If they make BitBucket issue tracking too complete they drive their own product, Stash, out of the market. Consider Stash's ridiculously low pricing for small teams if you want toys like this, plugins implement them.

    Edit: said Jira, meant Stash

  55. Malte Schwerhoff

    I am out of the office until and including 19th April. E-mails will not be forwarded. If you have questions regarding Viper or Silver, please contact Alex Summers (alexander.summers@inf.ethz.ch.

  56. José Campaña Aguilera

    Automattic have shown that the work place has to change with so much focus on Agile and dynamic cultures Bitbuket needs to integrate the options of continous development and control of code produced with the necesary analytics behind it to keep uptodate and help create these environments.

  57. Paul Friday

    Just moved to Bitbucket and I was surprised there is nothing there. Even if number of lines of code committed is not an ideal indicator of developer productivity, it does give an overview of what developers have been up to, which classes are frequently changed and should probably be broken up, and bad repo practices - infrequent commits. Used to use StatSVN and it was great for visualizing source.

  58. Ivan Henrique Tavares Pauletti

    A mass of customers asking for a simple solution (that competitors already have) being almost ignored since 2012. You can be mad with anyone who asks (I think it's the case here) but please let people give their feedback. O think Atlassian likes it more than you imagine, Captain America.

  59. Antoine Habert

    click on your BitBucket profile pic > click on Manage Account >> on the left panel click on "Find new add-ons" >> Install Awesome Graphs for Bitbucket by StiltSoft >> you now have a "Graph" option in your repo menu, with the same graphs as Github.

  60. Daniel Bennett staff

    We've spiked several implementations of this over the past couple of years and have settled on using our search index to provide the data for this feature. The only missing piece is the actual search index. Once issue #2874 (search) is close to completion we can start looking into implementing graphs using data stored there (plus some additional stuff, of course). The current ETA for having an actual ETA for search is approximately 6 months from now. I'll pop back in here in about 3 months with an update.

    FYI, everyone should check out the graphing add-ons. Or, if they're not to your liking, implement your own.

    Thanks,

    Dan Bennett, Bitbucket Development Manager

  61. Andrew Lundquist

    Thanks for the update Dan. The sooner the better. It would great to be surprised by something that happens way faster. The current options are not practically useful. Awesome Graphs has no contributor info and Git Guilt just doesn't work on larger repos. :(

  62. PepeAmpere

    Very nice job Kevin!

    Just btw, kind of out of scope, could you share with us amount of work put in that and estimate how much work it would be to do similar for HG repos?

  63. Kevin Wang

    @PepeAmpere It takes me about 1 month to work on this, mostly weekend and weekday nights. However for me I don't have to consider the infrastructure sizing for all BitBucket repositories. To support HG repos, code search is noting different than git. I haven't use HG for a while so I'm not sure the commit log can be mapped to exactly same as git or not.

    @tugay The addon installed will only work for your repositories. If your repository is under a team not your account, you have to install for that team instead of your account.

  64. Tri Nguyen

    @Kevin Wang There are a couple of addons that I saw earlier, one is called Git Guilt by Atlassian, another is called Awesome Graphs for Bitbucket by StiltSoft. Are these two combined similar to PowerGit? If so, I will remove those two and just use yours.

  65. Daniel Bennett staff

    Update: the search project is more-or-less on track. We should have a rough ETA for code search in March but as long as the infrastructure is there we might be able to tackle statistics before the code search is complete (indexing commits is faster than indexing all the code). I'll be updating the search issue around February and will update this issue around the same time.

  66. Obi-Wan Kenobi

    Not just stats, but I would like to see all the different repositories that I have worked on. My company has over 100 repositories on BitBucket. Trying to search through them and find which ones I have worked on it a pain.

  67. gitsense

    Disclaimer: GitSense is not affiliated with Atlassian and is a 3rd party solution provider

    It looks like the ETA for code search is July

    https://bitbucket.org/site/master/issues/2874/ability-to-search-source-code-bb-39

    but @Daniel Bennett has said they might be able to provide metrics sooner (March).

    However, if you can't wait and want code metrics now, we have something you may be interested in. In a week or two, we are going to start beta trials for our GitSense technology, which should provide you with the metrics that you are looking for. You can learn more about the front end at

    http://gitsense.bitbucket.org

    For the beta trial, we will provide you with our indexing technology, which you can use in the cloud for free, to index your private Git repositories. Sorry Mercurial is not supported. It is also important to note, GitSense does not provide pretty graphs, but rather it is focused on providing mineable raw data that you can plug into Excel, Tableau or any other Business Intelligence software.

    GitSense stores its indexed data in a SQL database and we want you to be able to slice and dice the data in a way that makes sense to you. We will provide a bunch of SQL templates that you can use like the following:

    SELECT 
        author_email,
        COUNT(id) AS num_commits
    FROM 
        z1_commits_1 GROUP BY author_email ORDER BY num_commits DESC LIMIT 5;
    

    which you can use to get the top 5 committers.

    GitSense also captures lines of code and code churn metrics that you can slice and dice as well. The following SQL script

    https://bitbucket.org/gitsense/gitsense-metric-examples/src/d585cec289cd68108f0ffc1d71607ca420bc01f2/weekly-file-loc.sql?at=master&fileviewer=file-view-default

    calculates the weekly lines of code for all markdown files on the master branch. Over time, we would like to make available dozens if not hundreds of ready to use SQL files that you can learn from/modify.

    So if you are interested in being able to data mine your Git repositories in the very near future (week or two), please send an email to privatebeta@gitsense.com

    Cheers

  68. Benjamin Echols staff

    We're still planning to use our search index to provide this type of data, but this would be a separate feature that comes after code search. Check out the code search issue (BB-39) for updates on progress there.

  69. C

    Bitbucket product owners, I cannot quantify developer code activity/footprint! This weakens my ability to manage. This goes against expectations.

    It is impractical for me to move my current project, but will probably start a new one in another service.

  70. Jason Kanaris

    Well, when a company sells themselves out to venture capitalists their priorities change... It's like this for a bunch of other highly up-voted features on other Atlassian products.

    Such a shame for something to happen to such a good company.

  71. Eric Henry staff

    Hey all, just a reminder that we don't use +1s to determine whether there is interest in a feature. Please use the "Vote for this issue" link at the top of the page.

    Additionally, several people have mentioned there is an add-on app that gives you this functionality. It is free, and works quite well.

  72. Mochnant

    Hopefully with 2,241 votes already it is clear this is a popular feature.

    The Awesome Graphs add-on does provide some of the functionality I hope Bitbucket will add, but is missing things I'd like to see (lines of code changes per contributor, code change frequency, etc) and also has its own problems (it times out frequently when loading the graphs and it not timezone aware so shows all commits in GMT).

  73. Eric B Jones

    Third party "apps" are not a substitute for first party features. BB's staff may think otherwise, but that's the reason for the amount of votes.

    Highly doubt we'll ever get this, but the +1 posts surely don't help. It's the reason why I have BB emails going to spam. :\

  74. Brendon LaRusic

    @Eric Henry

    In regards to voting, I have found no notice, explanation or documentation anywhere which expresses yours teams desire for this community to use the "vote" system. Except for this here blog post from 2013: https://blog.bitbucket.org/2013/08/14/no-more-1s-bitbucket-issues-now-has-voting/

    This is great and all, but for anyone new to BitBucket, or otherwise dont have an interest in your blog, how are we to know to use such a voting system? I mean, "+1" has become the default method of showing ones support or agreement with something on the internet. If you wish to change that, you should consider well, actually informing people.

    May I suggest you discuss with your team something like a notice at the top of issue pages that says "Hey, if you want this feature, be sure to use this handy voting system we have but decided not to tell you about -- until now".

    Better yet, why not just add in a simple check. If the comment contains nothing but "+1", dont allow a user to submit the comment and instead, display a nice little message saying "hey there! we have a voting system, please use that instead".

  75. Daniel Anechitoaie

    Better yet, why not just add in a simple check. If the comment contains nothing but "+1", dont allow a user to submit the comment

    Then people will add + 1 or ++, or bump or this. People always find a way of bypassing the system.

    Best is just to make it clear what comments are for and what votes are for. And that votes are taken into consideration. I think most people use comments instead of votes as they don't think there's someone checking periodically how many votes are and it just gets forgotten, but if they leave a message someone will get notified and so it will also get reminded about this.

  76. Brendon LaRusic

    Then forbid messages that attempt to post only + 1, ++, bump and this. Or, forget specifics and add in a health check of sorts, exactly as Stack does. I think it's safe to say its hard to express anything of significance in less than 10 characters -- and I Love You really has no context within BitBucket, so that doesn't count.

  77. Mochnant

    It would be nice if we could get an official response. Other than complaining about the use of "+1" comments, I don't see anything official since 2016-07-06, which is 1.5 years ago.

    Is this feature planned, being worked on, or has it been abandoned? This request as 2,303 votes and 503 comments. This is a highly requested feature that deserves an official response and timeline.

  78. Matt Ryall staff

    Hi all,

    Thanks for all the votes and recent comments on this issue. It's clear from all the enthusiastic discussions here that people are looking to get more visibility into the way their teams work, in order to work smarter and better. This is something we want to help you do with Bitbucket.

    However, this ticket has grown into a monster over the years. Looking at the comments above, many people want wildly different things, or even very specific requests that wouldn't be widely applicable.

    The original request, for basic author-level contribution stats, is now well covered by the Awesome Charts for Bitbucket Cloud add-on, which is freely available to all Bitbucket users. You can install it as an individual, and immediately get statistics on any repository you have access to. I've just tried it out now, and as a development manager myself, can see that this meets many of the needs for a quick report about top contributors on a repository.

    The team behind this add-on at StiltSoft is also a great partner for Atlassian, and supports dozens of extensions across our product suite for thousands of customers. They have been responsive in fixing the timezone issue highlighted above in this thread, and I'm sure will help with any further requests to expand contributor reporting in Bitbucket.

    Based on this, we now consider this ticket resolved. There is now an easy way to meet the original requester's needs. There are also many many ways to get statistics from your Git or Mercurial repo for the more advanced, more specific use cases described above (LOC counts, etc).

    To the point that this is an add-on rather than a core feature - Bitbucket and Atlassian as a whole spends a huge amount of time enabling and encouraging our ecosystem to fill feature gaps in our products. This is because despite having large teams on Bitbucket and our other products, we still can't do everything. Not even close. So rather than rebuilding what StiltSoft has already done a good job on, we're going to focus our efforts elsewhere in the product.

    At the moment, we're busy improving Bitbucket Cloud in the following areas:

    • pull requests
    • code search
    • pipelines & deployments
    • design and user experience.

    Based on your interest in this issue, I'm sure you will have some ideas of how we can make these better, especially around how we can provide high level visibility/statistics on how your teams are working together.

    So we'd love to see tickets submitted with ways we can help you understand more about how your team works in these areas. Maybe you want to know the lag time between PR creation and merge. Or deployment frequency to production. We'll be looking for useful statistics like these we can add as part of these feature improvements, and would love your feedback on what would help your team the most.

    Thanks again for your continued use and passionate enthusiasm for Bitbucket. It's this energy that keeps us going, trying to build the world's best code collaboration tool for your teams.

    Cheers,
    Matt and the Bitbucket team

  79. Andrei Karneyenka

    Matt, this was the No1 requested area of improvement on Bitbucket since 2012 (2200+ votes, No2 all-time high ) We've tried using Awesome charts as alternative and no offence - it's a neat plugin but being "a chart" it's pretty limited.

    Would be nice to hear why Bitbucket has no interest in a feature with so much public interest...

  80. eric cugota

    @Matt Ryall "using a 3rd party software" is in no way a solution to this issue. Awesome charts is great, but doesn't (for now) have a REST API or data export features.

    "Maybe you want to know the lag time between PR creation and merge. Or deployment frequency to production." OR MAYBE we want repository statistics and a way to access them from ERP's and project management software, be the format csv, xml,a working REST API, wathever, # built in # inside bitbucket.

    Remembers me when i asked to the IntelliJ AppCode team why there was no Interface editor built in, which forced us to keep both AppCode and Xcode open at the same time. their answer? "we're busy improving the reformat code features".

    in this case it's "Why isn't the most demanded feature by the active bitbucket issue community not a priority?" "becuse we're improving the milliseconds it takes a PR to create and merge".

    If one day a project or a client's requirements demand to have insight data on the development process, or we have to work with multiple dev teams at the same time, this will be a crucial feature that won't be small weighted when picking the platform to host the codebase. and ofcourse this doesn't mean that we won't keep using bitbucket, most of it it's awesome, and you're doing an amazing job. a job that would be better if instead of writing 8 paragraphs to explain "use a 3rd party,we won't do", the people at the steering wheel thought "maybe people are already satisfied by the performance and what we must improve is both UX and additional management features like this overly demanded one".

  81. Floris Kraak

    Awesome charts is lacking. The one thing our company needs from that is to have statistics on a team-wide basis. When you have hundreds of repositories only having per-repo graphs just doesn't cut it. On top of that, awesome charts is slow as a result of the architecture involved - Stiltsoft has no access to the repository until you give it to them, so there is no readily generated set of stats for them to show - it takes a lot of time. And that's just for one repo.

    It's possible to generate team-wide stats yourself with some shell magic to mass clone them and go over the log of each repository individually, but it's time consuming and a waste of precious developer resources. Plus it will never be as complete and awesome as something that can be generated by a dedicated team that has access to the full set of repositories. Like, say, Atlassian.

    So no, I do not consider this ticket resolved, either. You have a nice stopgap measure that satisfies people who don't do serious amounts of development on a serious amount of repositories. And maybe not even the people who only have one repository, either - because that may still be very very slow.

  82. Matt Ryall staff

    Thanks for the feedback, guys. I think my post covers most points, but want to address a couple of things in your comments:

    @Andrei Karneyenka - this was the No1 requested area of improvement on Bitbucket since 2012 (2200+ votes, No2 all-time high)

    Yes, and I'm sorry we haven't done a better job keeping you in the loop as our plans changed over the years. We're trying to get better at our issue triage, so you should see more frequent updates on highly voted tickets for Bitbucket in future.

    The search index idea mentioned above were an example of this. It just didn't pan out - we ended up needing an ElasticSearch index of current code for code search, which doesn't support commit statistics functionality at all. We should have come back sooner with a resolution on this ticket when that proved to be the case.

    @eric cugota - in this case it's "Why isn't the most demanded feature by the active bitbucket issue community not a priority?" "becuse we're improving the milliseconds it takes a PR to create and merge"

    With PR stats, I was talking about the hours or days from PR creation to merge, which is a cycle time indicator for your teams. But that's just a random idea. Better suggestions for specific stuff you'd like to (or already) measure to help improve dev team productivity are welcome.

    @Floris Kraak - The one thing our company needs from that is to have statistics on a team-wide basis.

    The original description of this ticket is clearly just for per-repository statistics, but different people following this ticket wanted different things. Unfortunately, it seems part of the reason this ticket has so many votes is because it covers so many things. We'll be trying to clarify and focus our public tickets as part of our triage process as well, so they don't end up like this in future.

    If you'd like to provide direct feedback about this change without emailing all 700 watchers on this ticket, I'm happy to take emails at mryall@atlassian.com around this issue or any other Bitbucket matter.

  83. Jagan Kaliyaperumal

    @Matt Ryall I tried awesome charts as well, it’s good for per repo basis, not when you want to see team-wide statistics or user statistics, like github’s heatmap for example. That alone would be an awesome feature if you guys could add it.

  84. Mochnant

    No offense to you personally, @Matt Ryall, but I consider this a lazy, poor decision. If the best Bitbucket can do is point to a 3rd party app that does not meet many of the requested features, it's clear that the product is not going to be viable for the long term. Have you seen the stats that are being offered to development managers on github and other services?

    Unfortunately, in light of this, I don't see any option for my team but to use one of these other services.

  85. Marios Vasiliou

    @Matt Ryall No offense but i agree that the issue is not resolved status...It is a wont solve status! If the best solution for bit-bucket is to redirect users to a third party paid application i am very sorry but you are not professional!

    Not all private companies want to add integrations and give full access in their code from a company that they don't know or pay for services that your competitors have already implement and are available for free!

    If a feature request with 2325 votes and open for so many years and hundred of watchers is less significant that adding beta features like file details what can i say.... you are going to the wrong direction! We don't want a representative of bit-bucket to recommend a paid alternative after 6 years... We want a solution that everyone has except Bitbucket! I am sorry but if Bitbucket doesn't start listening to customers my company will leave also.... Trello and file details are not features for business customers....Code review tools and Contributing statistics are....

  86. Matt Ryall staff

    Thanks for your comments. I wanted to add some important clarifications (emphasis mine):

    But the "Awesome Graphs for Bitbucket server" costs a lot ...

    This issue and everything in the site/master issue tracker is for Bitbucket Cloud. If you're after Bitbucket Server features, you should be watching the BSERV issue tracker on jira.atlassian.com, alongside the rest of our products. (Bitbucket Cloud issues are here mainly for historical reasons, and are planned to move there in the near future too.)

    If the best solution for bit-bucket is to redirect users to a third party paid application …

    Awesome Graphs for Bitbucket Cloud is free.

  87. John Cornett

    @Matt Ryall - One concern I have about third party addons and externally developed software is security. When you use external software, you are allowing a 3rd party into your intellectual property which is private and may belong to customers who've spent $100k - $1M+ on the IP. I would much prefer that feature coming from Atlassian whom I have an agreement with and can hold accountable if security is breached. If you are viewing long term, source control will continue to escalate in prominence as well in terms of security and control, as it is at the forefront of what drives technological advancement. It's not just devices and hardware, but more importantly the code. What assurance do I have when I have to grant permission to a 3rd party to read my code? I have no idea what they're doing with it. That doesn't sit well with me.

    On your priorities: I think pull requests are fine. Search does need to improve...a lot. Professional teams can and should manage their own CI/CD...that's a massive vertical to shove into your product mix. The UI/UX evolution should be incremental and imperceivable...change may be necessary (when driven my users, not your designers) but it agitates and confuses users.

  88. Marios Vasiliou

    @Matt Ryall paid or free the main point is the same...its a third party application from a company that we dont trust as a company to share our data and give access. GDPR is coming and we cant share data freely. A private company will not trust sisoft to share codebase...but will trust attlasian and bitbucket which already does. That feature should be on bitbucket priority list and give a solution instead of recommendation after so many years. If you want to gain some clients you have to give at least the same features as other competitors have and more...not less features and more recommendations for third party addons that are not even similar to competitor...

  89. eric cugota

    Good day @Matt Ryall .

    "With PR stats, I was talking about the hours or days from PR creation to merge, which is a cycle time indicator for your teams. But that's just a random idea. Better suggestions for specific stuff you'd like to (or already) measure to help improve dev team productivity are welcome."

    Dev productivity isn't hard to improve: atlassian provided authenticated REST API of stats per user, team, repository and project, locs per user, locs per team, time between commits, commits per user, commits per team, locs per commit and let product managers shuffle mix and manage this data on their own way. there is no single better thing the grand scheme of things of productivity than to be able to notice your team's strenghts, weaknesses, what projects are burdening you in time, what external or itnernal teams mess up stuff... data, data, and data. and no, a graph in bitbucket or JIRA is not even near to it.Awesome graphs is good for small projects, it's pretty cool, but it's binded and tied to a repository it must scan, and the data it provides is limited due to the fact that the people that should be providing this data isn't.

  90. Mochnant

    Does anyone tracking this ticket know if there are other, open enhancement requests we can move this discussion to? It is clear this issue is not actually resolved at all, but just swept under the carpet. The best way we can get it addressed is to keep the pressure on.

  91. James Mills

    @Mochnant The reality is there is likely little to no "business value" added to Atlasssian to build this feature and the development/support costs involved.

    James Mills / prologic

    E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au

  92. Log in to comment