Defect #6313
REST API Only Exposes a Limited Sub-Section of Issues
| Status: | Closed | Start date: | 2010-09-06 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | REST API | |||
| Target version: | - | |||
| Affected version: | 1.0.1 | Resolution: |
Description
This likely is me just doing something stupid, but no matter what I try I can't seem to get anything even close to the full issue list out of the REST API. Whether I use the API (Issue.find(:all)) or just go to the URLs directly in my browser (ourRedmine.com/issues.xml), all I get back is 25 issues. This is hardly ":all" :-( I thought this might be a pagination issue, so I tried (in the browser) "@ourRedmine.com/issues.xml?page=2", but I still get the same results.
So, either I'm doing something stupid (again, very likely), or whoever created the REST API didn't bother to test a Redmine installation with more than 25 issues ...
History
Updated by Jeremy Walker over 1 year ago
This is probably obvious, but just to clarify, when I said "user the API", I meant "ActiveResource".
Updated by Jeremy Walker over 1 year ago
gah, use not user; I wish you could edit on here ...
Updated by Jeremy Walker over 1 year ago
I have found that by doing:
Issue.find(:all, :params=>{:per_page => 200})I can now get 200 issues. Unfortunately however, this is not a true "limit" parameter, as I can't do (for instance):
Issue.find(:all, :params=>{:per_page => 300})
So, I still don't have a way to use the webservice to actually, y'know, get our issues, but at least now I can get the first 200 of them rather than the first 25.
Updated by Jeremy Walker over 1 year ago
- Status changed from New to Resolved
Inexplicably, the page parameter started working today; I have no idea why (I swear it wasn't working when I filed this issue). Closing issue.
Updated by Felix Schäfer over 1 year ago
- Status changed from Resolved to Closed