REST API: Issues no longer report Comment Count

Issue #9669 resolved
Anonymous created an issue

As of 6/8/2014, using the 1.0 API, retriving a list of issues for a repository no longer reports the comment count which it used to. Log file has been attached. I would assume that since API 2.0 is being work on the 1.0 API would stop changing. However, this is not the first time a breaking change has been introduced into 1.0 without there being a suitable replacement in 2.0. Why has this occured?

Comments (7)

  1. Zachary Davis

    You are correct that we do not return comment_count in the issues list response, for performance reasons. However, this has been the case for quite some time, and has not changed recently. comment_count is still returned for individual issues.

  2. Kaleb Elwert

    I'm not sure I understand. We haven't returned that data for quite some time. We did however update the documentation last week to properly reflect this. Do you have an application that relies on these counts that broke?

  3. Dillon

    Hey Kaleb, I develop the iOS BitBucket application CodeBucket which I used the comment_count that was present when you return a list of issues to display the comment # so it could be filtered or sorted by, etc...


    Unfortunately, I didn't find the bug and one of the users pointed it out to me that all the items were returning 0 for comment count. In addition, while I can still get the number of comments by directly accessing the issue it makes sorting and filtering and grouping a bitch. The same goes for, what used to be, the watchers and forks that used to exist in the repository objects when you listed them. With the absence of these fields it just makes it harder to organize data for the user especially if there's no REST parameter that would replace it.

  4. Log in to comment