Skip to end of metadata
Go to start of metadata

Overview

The issues resource provides functionality for getting information on issues in an issue tracker, creating new issues, updating them and deleting them. You can access public issues without authentication, but you will only receive a subset of information, and you can't gain access to private repositories' issues. By authenticating, you will get a more detailed set of information, the ability to create issues, as well as access to updating data or deleting issues you have access to.

FieldDescription
countAn integer representing the count of issues returned.
filterA string representing a filter applied to a search.
searchA string containing a search term.
issuesAn array of issue structures.

An issue structure contains the following fields.

FieldDescription
status

A enumerator representing the issue status. Valid status values are:

  • new  
  • open
  • resolved
  • on hold
  • invalid
  • duplicate
  • wontfix
priority

A enumerator representing the issue priority. Valid priority values are:

  • trivial
  • minor
  • major
  • critical
  • blocker
titleA string containing the issue title.
reported_byContains the profile for the user that reported the issue.
utc_last_updatedA Universal Timestamp Coordinate representing the last time the issue was updated.
comment_countAn integer representing the number of comments on the issue.
metadata

A structure containing the following:

kind

This is equivalent to the Type value in the GUI. It can take any of the following values:

  • bug
  • enhancement
  • proposal
  • task
versionA user defined enumerator value.
componentA user defined enumerator value.
milestoneA user defined enumerator value.
contentA string containing the issue description.
created_onThe timestamp from the Bitbucket server.
local_idAn integer representing the id for this issue tracker.
follower_countAn integer for the number of followers.
utc_created_onA Universal Timestamp Coordinate timestamp for the issue creation.
resource_uriA URI for the issue.
is_spamA boolean indicating if the issue is spam or not. The Bitbucket service uses Akismet to protect its users from spam. When Akismet indicates a comment may be spam, Bitbucket sets is_spam to true.

When getting a list of issues, you can apply a filter to the issues. The Bitbucket service supports the following filter operators:

Operator

Definition

~

contains
 !~

doesn't contain

 ^

begins with

 $

ends with

 !

is not

Not applicable

is

When constructing your parameter string, combine one of the issue fields as a parameter and the operator in the parameter value. The following table illustrates some examples of how to construct a parametized filter:

ParameterValueNotesWhat the filter will look like:
statusopenstatus is open
status=open&kind=!bug&title=~work
kind!bugkind is not bug
title~worktitle contains work

A curl call using this filter looks like this:

curl https://bitbucket.org/api/1.0/repositories/jespern/django-piston/issues?status=open&kind=!bug&title=~work
 When the call returns, it lists the count of matching issues the filter found (in this case 1).

You can query for multiple instances of the same parameter. The system treats multiple instances of the same parameter as an OR for the overall filter query. For example, the following filter looks for open and resolved bugs with the word for in the title:

status=open&kind=!bug&status=resolved&title=~for 

The filter operators do not work with all of the possible issue fields. The following table lists the fields you can filter on and which operators work with them.

Issue Field

Supported Filter Operators

title

All

content

All

version

is and ! ( is not)

milestone

is and ! ( is not)

component

is and ! ( is not)

kind

is and ! ( is not)

status

is and ! ( is not)

responsible

is and ! ( is not)

reported_by

All

To simply search through the issues for a phrase, supply a simple search parameter with a string value:

curl https://bitbucket.org/api/1.0/repositories/jespern/django-piston/issues?search=each+thread

Use the + (plus sign) to indicate a space in the search phrase.

GET a list of issues in a repository's tracker

Gets the list of issues in the repository.  If you issue this call without filtering parameters, the count value contains the total number of issues in the repository's tracker.  If you filter this call, the count value contains the total number of issues that meet the filter criteria.

Authorization is not required for public repositories with a public issue tracker. Private repositories or private issue trackers require the caller to authenticate with an account that has appropriate authorisation. By default, this call returns 15 issues. If necessary you can specify the sort parameter to order the output. 

You can supply any of the following parameters to this call:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
limitNoAn integer specifying the number of issues to return. You can specify a value between 0 and 50. The default is 15.
startNoOffset to start at. The default is 0 (zero).
searchNoA string to search for.
sortNo

Sorts the output by any of the metadata fields. Enter a name value pair similar to the following:

sort=milestone

title

No

Contains a filter operation to restrict the list of issues.

content

No

Contains a filter operation to restrict the list of issues.

version

No

Contains an is or ! ( is not) filter to restrict the list of issues.

milestone

No

Contains an is or ! ( is not) filter to restrict the list of issues.

component

No

Contains an is or ! ( is not) filter   to restrict the list of issues.

kind

No

  Contains an is or ! ( is not) filter   to restrict the list of issues.

status

No

  Contains an is or ! ( is not) filter  to restrict the list of issues.

responsible

No

  Contains an is or ! ( is not) filter   to restrict the list of issues.

reported_by

No

Contains a filter operation to restrict the list of issues.

 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues?parameter=value&parameter=value&...
 Click here to expand...

GET an individual issue

Gets in individual issue from a repository. Authorisation is not required for public repositories with a public issue tracker. Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}
 Click here to expand...

GET a list of an issue's followers

Gets the followers for an individual issue from a repository. authorisation is not required for public repositories with a public issue tracker. Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}/followers
 Click here to expand...

POST a new issue

Creates a new issue in a repository. This call requires authentication. Private repositories or private issue trackers require the caller to authenticate with an account that has appropriate authorisation. The authenticated user is used for the issue's reported_by field.

FieldRequiredDescription
statusno

A enumerator representing the issue status. Valid status values are:

  • new  
  • open
  • resolved
  • on hold
  • invalid
  • duplicate
  • wontfix
priorityno

A enumerator representing the issue priority. Valid priority values are:

  • trivial
  • minor
  • major
  • critical
  • blocker
titleyesA string containing the issue title.
responsiblenoThe accountname of the person responsible for this issue.
contentnoA string containing the issue description. You'll need URL encode the content string.
kindno

This is equivalent to the Type value in the GUI. It can take any of the following values:

  • bug
  • enhancement
  • proposal
  • task
componentnoA string containing a component value. These values are defined by the repository administrators.
milestonenoA string containing a milestone value. These values are defined by the repository administrators.
versionnoA string containing a version value. These values are defined by the repository administrators

 POST https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues  --data "title=value&content=value"
 Click here to expand...

Update an existing issue

Updates an existing issue. Updating the title or content fields requires that the caller authenticate as a user with write access. For other fields, the caller must authenticate as a user with read access. Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Field
Required?
Description
accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

statusNo

A enumerator representing the issue status. Valid status values are:

  • new  
  • open
  • resolved
  • on hold
  • invalid
  • duplicate
  • wontfix
priorityNo

A enumerator representing the issue priority. Valid priority values are:

  • trivial
  • minor
  • major
  • critical
  • blocker
titleNoA string containing the issue title.
responsibleNoThe accountname of the person responsible for this issue.
contentNoA string containing the issue description.
kindNo

This is equivalent to the Type value in the GUI. It can take any of the following values:

  • bug
  • enhancement
  • proposal
  • task
componentNoA string containing a component value. These values are defined by the repository administrators.
milestoneNoA string containing a milestone value. These values are defined by the repository administrators.
versionNoA string containing a version value. These values are defined by the repository administrators

PUT https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}  --data "parameter=value&parameter=value"
 Click here to expand...

DELETE an issue

Deletes the specified issue_id. Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

DELETE https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}

This call returns 204 no content on a successful operation.

GET the comments for an issue

Gets the array of comments on the specified issue. An issue has the following fields:

FieldDescription
contentThe content of the comment.
author_infoThe account profile of the user that added the comment. Only Bitbucket account holders can comment on issues.
comment_idAn integer representing an id for the comment. This is created by Bitbucket.
utc_updated_onA Universal Timestamp Coordinate timestamp for the last time the comment was updated.
utc_created_onA Universal Timestamp Coordinate timestamp for the comment creation.
is_spamA boolean indicating if the issue is spam or not. The Bitbucket service uses Akismet to protect its users from spam. When Akismet indicates a comment may be spam, Bitbucket sets is_spam to true.

 Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}/comments
 Click here to expand...

GET an individual comment

Gets an individual comment on an issue. Private repositories or private issue trackers require the caller to authenticate  with an account that has appropriate access. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

comment_idYesThe comment identifier.
GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}/comments/{comment_id}
 Click here to expand...

POST a new comment on the issue

Creates a new comment on an issue using the specified contentdata. The caller must be authenticated and have access to the issue tracker to create an issue. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

contentYesThe comment.

POST https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}/comments --data "content=string"
 Click here to expand...

Update a comment

Updates a comment on an issue using the specified content data. The caller must be authenticated as a user that created the comment or as a user with administrative rights on the repository. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.

issue_id

Yes

The issue identifier.

comment_idYesThe comment identifier.
contentYesThe comment.

PUT https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/{issue_id}/comments/{comment_id} --data "content=string"
 Click here to expand...

GET the components defined on an issue tracker

Gets an array of the components associated with the issue tracker. Components have the following fields:

FieldDescription
object_idThe component's absolute ID (the database ID—a repository's first component will not have an ID of 1).
nameThe component's name. A name cannot exceed 128 characters and must be unique. The issue tracker is case sensitive — it considers Release and release to be unique names.

To get the list of components, private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/components
 Click here to expand...

GET an individual component

Gets an individual component in an issue tracker. To get a component, private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/components/{object_id}
 Click here to expand...
{
    "name": "api",
    "id": 37
}

POST a new component in an issue tracker

Creates a new component in an issue tracker. You must supply a namevalue in the form of a string. The server creates the id for you and it appears in the return value. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
nameYesThe component name to create.
repo_slugYesThe repository identifier.
POST https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/components --data "name=String"
 Click here to expand...
{
    "name": "gui",
    "id": 908
}

Update an existing component

Updates an existing component in an issue tracker. You must supply a name value in the form of a string. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
nameYesThe component name to create.
object_idYesThe component identifier.
PUT https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/components/{object_id} --data "name=String"
 Click here to expand...

DELETE a component from the issue tracker

Deletes a component in an issue tracker. Keep in mind that the component can be in use on existing issues. When you delete a component, the system updates the issues and does the following:

  • remove the component type
  • leaves the issue's component value empty
  • adds a comment to the issue explaining the change

To delete a component, public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component to delete.
DELETE https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/components/{object_id}

This call returns the following on succes:

HTTP/1.1 204 NO CONTENT

GET a list of versions

Gets an array of the versions associated with the issue tracker. Versions have the following fields:

FieldDescription
object_idThe version's absolute ID (the database ID—a repository's first component will not have an ID of 1).
nameThe version name. A name cannot exceed 128 characters and must be unique.

To get the list of versions, private issue trackers require the caller to authenticate with an account that has appropriate authorisation.   This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/versions
 Click here to expand...

GET an individual version

Gets an individual version in an issue tracker. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/versions/{object_id}
 Click here to expand...

POST a new version

Creates a new version in an issue tracker. You must supply a name value in the form of a string. The server creates the id for you and it appears in the return value. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
nameYesThe version name to create.
POST https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/versions --data "name=String"
 Click here to expand...
{
    "name": "2.0",
    "id": 9108
}

PUT an update to a version

Updates an existing version in an issue tracker. You must supply a name value in the form of a string. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
nameYesThe version name to create.
 PUT https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/versions/{object_id} --data "name=String"
 Click here to expand...

DELETE a version

Deletes a version in an issue tracker. Keep in mind that the version can be in use on existing issues. When you delete a version, the system updates the issues and does the following:

  • remove the version type
  • leaves the issue's version value empty
  • adds a comment to the issue explaining the change

To delete a version, public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
DELETE https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/versions/{object_id}

This call returns the following on success:

HTTP/1.1 204 NO CONTENT

GET the defined milestones

Gets an array of the milestones associated with the issue tracker. Milestones have the following fields:

FieldDescription
object_idThe milestones absolute ID (the database ID—a repository's first milestone will not have an ID of 1).
nameThe version name. A name cannot exceed 128 characters and must be unique.

To get the list of milestones, private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/milestones
 Click here to expand...

GET an individual milestone

Gets an individual milestone in an issue tracker. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
 GET https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/milestones/{object_id}
 Click here to expand...

POST a new milestone

Creates a new milestone in an issue tracker. You must supply a name value in the form of a string. The server creates the id for you and it appears in the return value. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
nameYesThe version name to create.
POST https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/milestones --data "name=String"
 Click here to expand...

PUT an update to milestones

Updates an existing milestone in an issue tracker. You must supply a name value in the form of a string. Public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
nameYesThe version name to create.
PUT https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/milestones/{object_id} --data "name=String"
 Click here to expand...

DELETE a milestone

Deletes a milestone in an issue tracker. Keep in mind that the milestone can be in use on existing issues. When you delete a milestone, the system updates the issues and does the following:

  • remove the milestone type
  • leaves the issue's milestone value empty
  • adds a comment to the issue explaining the change

To delete a milestone, public and private issue trackers require the caller to authenticate with an account that has appropriate authorisation. This method has the following parameters:

Parameter

Required?

Description

accountnameYesThe team or individual account owning the repository.
repo_slugYesThe repository identifier.
object_idYesThe component identifier.
DELETE https://bitbucket.org/api/1.0/repositories/{accountname}/{repo_slug}/issues/milestones/{object_id}

This call returns the following on succes:

HTTP/1.1 204 NO CONTENT

 

 

30 Comments

  1. Is there a way to get a list of users an issue can be assigned to?

    1. You could get a list of groups with privileges on a repository (groups-privileges) and determine this list from the group membership.

      1. Unfortunately, querying the groups-privileges of a repository requires that "The caller must authenticate as a user with administrative rights on the account." This seems like it would be the case if you were making modifications to the group-privileges but I am curious on why simply querying it requires administrator rights. Do you believe this is correct? Otherwise, there doesn't seem to be a way to mimic the web version's "Asignee" field when assigning tickets (since it drops down with all the users of the repository regardless if you are an administrator or just a nobody.)

        1. Dillon,  I checked the code, it looks like we are requiring you to have ownership of the account or admin on the repository.  I'll ask the team when they get in and see if there is something I'm missing...it does seem this should be doable.

          Mary

          P.S. Well, I asked an there is nothing additional.  Please file an enhancement request if you still need this. Sorry not to have a better answer.

  2. When getting a list of issues from a repository, is it possible to sort ascending vs descending? Querying issues can take a "sort=<value>" argument, however, it always seems to be in ascending order. Is it possible to change that?

    1. Dillion,

      You must be referring to the ability to click the column orders an issue list page. You want something similar in the returned REST data.  There isn't a sort ability from the REST call. Right now, this is provided by the page's underlying Javascript.

      Mary 

    2. I wanted to do this same thing. I inspected the source on the website and found they prepend "-" to the value to get the reversed sort. I tried it with the API and it worked! For example:

      https://bitbucket.org/api/1.0/repositories/cheryl/test-git/issues/?sort=-utc_created_on

      1. Hey Cheryl, Thanks for checking that...should have checked myself. I'll update the docs.

  3. Is there a way to get the default milestone?

    1. We don't return this.  There should be a way to see that.  Can you file an enhancement request for this? They have more impact when they come direct from customers.

  4. Is there a way to retrieve the issue_id of a POST a new issue.

  5. Is the API (partally) compatible to any bug tracker?
    What bug tracker can I select in LaunchPad for the Bitbucket tracker?

    1. Simon,  I'm not sure I understand your question.  The API returns raw issue data; your client code would need to handle that data.  Can you give me an example of what you are trying to do?

      1. Mary, thanks for your reply.

        I would like to register the bug tracker in a project on www.launchpad.net. There is a long list of bug trackers to select from, but no one is named bitbucket.

        1. Hi Simon,  

          Launchpad.net only supports certain types of trackers. 

          Bitbucket isn't one of them.  Launchpad would need to write an integration to our tracker.  You should contact support at Launchpad and ask them about this.

          Mary

  6. Is there a way to create an issue with a specific issue_id (assuming there is no such issue).

    Or is there a way to turn the Update issue call to create the issue if it doesn't exists? 

    1. The system creates the issue ID. So, you can't specify that.  If there is a  way to update and specify the ID, that would most likely be a bug.

  7. Anonymous

    Hi,

    how do I send multi-line content for a new issue? When I place "\r\n" in the content field it gets replaced by \\r\\n in the issue and will not show up properly.

    1. You need to URL encode the comment before you send it.   I'll add this to the documentation.

  8. Anonymous

    Hi ,

    Is there a way to get all the issues in an excel sheet?

    1. You can export the issues. See Export or import issue data for more information.

  9. Hi, 

    I tried to Post a new comment on Issue, but i always get status code 403, i use afnetworking 2.0 , my request header use key:"Authorization" value : "token" + myTokenNumber, there is no problem to Get comments,

    i also try on Postman Chrome extension and get status :

    CSRF verification failed. Request aborted.

    You are seeing this message because this HTTPS site requires a 'Referer header' to be sent by your Web browser, but none was sent. This header is required for security reasons, to ensure that your browser is not being hijacked by third parties.

    If you have configured your browser to disable 'Referer' headers, please re-enable them, at least for this site, or for HTTPS connections, or for 'same-origin' requests.

     

    what should i do , thanks

     

     

    1. You need to send a Referer Header. It could be Chrome is not sending this.  Did you try the call with curl?

      http://stackoverflow.com/questions/14235377/http-referer-and-bookmark

      1. can u give example curl post comment with oauth_token (not username password) thanks

  10. I'm not seeing 'comment_count' returned by the GET repo/issues result anymore. Was it removed? I've confirmed the issue does have comments on my end, and the key is returned when I view an issue directly.

  11. It looks like just recently you are no longer able to unassign an existing issue. Any attemps, like sending empty data for that field, results in the same username being responsible after update. This used to work but now is broken. I have filed a ticket: https://bitbucket.org/site/master/issue/9010/rest-api-10-cannot-unassign-issue which I hope gets addressed quickly since not being able to unassign issues is a bit of a pain...

  12. As of 6/8/2014, returning a list of issues no longer reports the comment count - it has been completely removed. Why does the 1.0 API keep changing? I would assume that If you're working on a 2.0 API there should be no changes to the 1.0...

    1. Thanks for taking the time to comment. You are correct, we removed the comment and follower count from GET a list of issues in a repository's tracker in October of 2013. It was removed because this was so resource intensive as to outweigh the benefit it provided. You can still get comment and follower count's by calling for an individual issue like so:

      I hope this helps resolve this for you and apologize any inconvenience this caused you. 

       

  13. Hi, is there a way of getting number of votes for each issue? it is displayed in the issue tracker view but could not find any reference in the API. Thanks.

    1. Hello,

      At this time you have to use the site to see or post votes for an issue there is no API interaction for that. Feel free to open a Feature request.

      Thanks for taking the time to comment!