•  
      request #9660 get /projects/{id}/trackers | returns incorrect number of tracker define in project
    Infos
    #9660
    Joseph Guagenti (joseph.guagenti)
    2024-01-30 16:00
    2016-11-16 19:14
    9935
    Details
    get /projects/{id}/trackers | returns incorrect number of tracker define in project
    get /projects/{id}/trackers is returning one less tracker then what is defined in the project. In attached images please note there are 11 trackers in the web interface.
    
    Bugs ( 0 total ) Epics ( 2 open / 2 total )
    Features ( 9 open / 9 total ) 
    Kanban Tasks ( 0 total ) 
    Project Charter ( 1 open / 1 total ) 
    Releases ( 0 total ) 
    Request New Feature ( 0 total ) 
    Sprints ( 0 total ) 
    Stories ( 11 open / 11 total ) 
    Tasks ( 17 open / 17 total ) 
    Testing ( 5 open / 5 total ) 
    In the REST API it only returns 10 trackers 
    Bugs
    Epics
    Features
    Kanban Tasks
    Project Charter
    Releases
    Request New Feature
    Sprints
    Stories
    Tasks
    We are missing the last tracker: 
    Testing

    JSON

    [
       {
          "id":179,
          "uri":"trackers/179",
          "html_url":"/plugins/tracker/?tracker=179",
          "project":{
             "id":111,
             "uri":"projects/111",
             "label":"IBN-EMP Sales Order Entry Pad"
          },
          "label":"Bugs",
          "description":"Bugs Tracker",
          "item_name":"bug",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"fiesta_red"
       },
       {
          "id":180,
          "uri":"trackers/180",
          "html_url":"/plugins/tracker/?tracker=180",
          "project":{ },
          "label":"Epics",
          "description":"Epics are a collection of features.\r\n* Logical Grouping of Features",
          "item_name":"epic",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"plum_crazy"
       },
       {
          "id":181,
          "uri":"trackers/181",
          "html_url":"/plugins/tracker/?tracker=181",
          "project":{ },
          "label":"Features",
          "description":"Features - Are services provided by the system that fulfill stakeholder needs. In most cases a Feature should be a testable function independent of the full project.",
          "item_name":"feature",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"deep_blue"
       },
       {
          "id":182,
          "uri":"trackers/182",
          "html_url":"/plugins/tracker/?tracker=182",
          "project":{ },
          "label":"Kanban Tasks",
          "description":"A tracker of tasks for kanban",
          "item_name":"kanbantask",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":null,
          "resources":[ ],
          "color_name":"inca_silver"
       },
       {
          "id":183,
          "uri":"trackers/183",
          "html_url":"/plugins/tracker/?tracker=183",
          "project":{ },
          "label":"Project Charter",
          "description":"Project Charter defines the detail and objective of the project. There are 2 section defined for clients approval:\r\n\r\n1. \"Project Charter\" to captures the vision of the Client\r\n* Provides a Vision of project\r\n* Goals and Dependencies\r\n* Scope both In-Scope and known Out-of-Scope\r\n* Known Constraints and Known Risks\r\n* Agreement to move forward with \"Project Plan\", \"Discovery\" and to pay the cost of doing so\r\n\r\n\r\n2. \"Project Plan Estimation\"\r\n* Discovered Constraints and Discovered Risks\r\n* Create Features list\r\n* Define Epic Stories\r\n* Layout User Stories\r\n* Estimate Tasks and assign hours to each Tasks\r\n* \"Project Plan Sign Off\" agreement to begin and pay the cost",
          "item_name":"Charter",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":null,
          "resources":[ ],
          "color_name":"clockwork_orange"
       },
       {
          "id":184,
          "uri":"trackers/184",
          "html_url":"/plugins/tracker/?tracker=184",
          "project":{ },
          "label":"Releases",
          "description":"releases",
          "item_name":"rel",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":null,
          "resources":[ ],
          "color_name":"sherwood_green"
       },
       {
          "id":185,
          "uri":"trackers/185",
          "html_url":"/plugins/tracker/?tracker=185",
          "project":{ },
          "label":"Request New Feature",
          "description":"Request a New Feature to be added to the product or solution.",
          "item_name":"request",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":null,
          "resources":[ ],
          "color_name":"chrome_silver"
       },
       {
          "id":186,
          "uri":"trackers/186",
          "html_url":"/plugins/tracker/?tracker=186",
          "project":{ },
          "label":"Sprints",
          "description":"sprints",
          "item_name":"sprint",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"acid_green"
       },
       {
          "id":187,
          "uri":"trackers/187",
          "html_url":"/plugins/tracker/?tracker=187",
          "project":{ },
          "label":"Stories",
          "description":"User Stories",
          "item_name":"story",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"lake_placid_blue"
       },
       {
          "id":188,
          "uri":"trackers/188",
          "html_url":"/plugins/tracker/?tracker=188",
          "project":{ },
          "label":"Tasks",
          "description":"task",
          "item_name":"task",
          "fields":[ ],
          "structure":[ ],
          "semantics":{ },
          "workflow":{ },
          "parent":{ },
          "resources":[ ],
          "color_name":"flamingo_pink"
       }
    ]

     

     

    API
    Empty
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2024-01-30
    Attachments
    References
    References list is empty

    Follow-ups

    User avatar
    no offset and no limit set. If i recall setting the limit greater then the
    number of trackers to fix the issue. So as a quick fix limit on the
    trackers is set to 30.
    how it should work... if no limit is set ALL data should be returned. Let
    the coder set the offset and limit if they feel they need to get the data
    in blocks.



    On Wed, Jan 25, 2017 at 9:33 AM Tuleap <forge__artifacts@tuleap.net> wrote:

    [citation removed]
    User avatar
    Hello,

    What are the value of the offset and the limit provided by your REST API call ?

    • Status changed from New to Waiting for information
    • Reported in version cleared values: 9.0