•  
      request #12620 /plannings/{id}/milestones returns wrong x-pagination-size
    Infos
    #12620
    Joseph Guagenti (joseph.guagenti)
    2018-12-14 13:40
    2018-12-12 16:22
    12531
    Details
    /plannings/{id}/milestones returns wrong x-pagination-size

    x-pagination-size is returning x-pagination-limit. There are 75 milestones in project 101.

    x-pagination-size(75) > x-pagination-limit(10) = x-pagination-size(10) > x-pagination-limit(10

    x-pagination-size(75) > x-pagination-limit(60) = x-pagination-size(60) > x-pagination-limit(60

    ------------------------------------------------

    if x-pagination-limit is greater then x-pagination-size then correct x-pagination-size is returned:

    x-pagination-size(75) > x-pagination-limit(100) = x-pagination-size(75) > x-pagination-limit(100

    Empty
    API (SOAP|REST)
    All
    Empty
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2018-12-14
    Attachments
    References

    List of items referenced by or referencing this item.

    Artifact Tracker v5

    Follow-ups

    • User avatar
      gerrit #13447 integrated into Tuleap 10.8.99.76.

      • Status changed from Under review to Closed
      • Connected artifacts
      • Close date set to 2018-12-14
    • User avatar
      A patch is under review: gerrit #13447.

      • Status changed from Under implementation to Under review
    • User avatar
      • Status changed from Verified to Under implementation
    • User avatar
      Hi,

      Thanks for the report, you are right the X-Pagination-Size value is incorrect for this route.

      • Status changed from New to Verified
      • Assigned to changed from None to Thomas Gerbet (tgerbet)
      • Reported in version changed from 10.8 to All
      • Platform cleared