My mistake. It turns our I misread the pagination docs (because the returned values are sorted by state & creation date, my closed issues for closed milestones happened to appear near the end & were cut off; I didn't notice that some of the issues for unclosed milestones were also missing).
Tip for future API users: if you're trying to retrieve all issues, you will need to perform multiple queries for each page, if the number of issues returned = the per_page parameter. On Wednesday, March 5, 2014 1:29:47 PM UTC-5, Ali Tavakoli wrote: > > When I do a GET to http://<my host>/api/v3/projects/:project_id/issues, it > returns an incomplete list of issues. > > When I do a GET specifically for one of those missing issues by id > (http://<my > host>/api/v3/projects/:project_id/issues/:missing_issue_id), I get > information for that issue back. > > The one thing I noticed was that the missing issues were all assigned to a > recently-closed milestone, and I think this started happening after an > upgrade was performed (with the milestone having been closed prior to that > upgrade), but I'm not sure. > > Has anyone else run into this problem? I can provide more specific > information as needed. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
