REST API - Add status to issues metadata

Barthelemy Dagenais avatarBarthelemy Dagenais created an issue

The json data returned for a specific issue or for a list of issues does not indicate the status of the issue (e.g., new/open/closed).

As far as I know, there is no way to determine the status of an issue through the REST API. Something like that would be useful:

curl https://api.bitbucket.org/1.0/repositories/qualyzer/main/issues/63/                                                                           
{                                                                                                                                                                 
    ...                                                                                                                                     
    "created_on": "2010-08-06 16:48:54",                                                                                                                          
    "local_id": 63,                                                                                                                                               
    "follower_count": 1,                                                                                                                                          
    "metadata": {                                                                                                                                                 
        "kind": "enhancement",                                                                                                                                    
        "version": "0.1",                                                                                                                                         
        "component": "Core",                                                                                                                                      
        "milestone": "1.0",
        "status": "resolved",                                                                                                                                   
    },
    ...                       

Comments (5)

  1. Erik van Zijst

    Hi Barthelemy, this has been reported before and I agree we should add that. We've got an issue for it on our internal issue tracker and hope to address it soon. When we do, it will be mentioned on our blogs.

    Cheers, Erik

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.