Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filter operation with no status_id parameter set found no closed issues. #136

andrius-momzyakov opened this issue Jun 27, 2016 · 2 comments


Copy link

@andrius-momzyakov andrius-momzyakov commented Jun 27, 2016

I'm using Redmine 2.5.2.
Tried to iterate over all issues for a given project with
for issue in rm.issue.filter(project_id='portal'):
but discovered that it returned open issues only.
In Docs it's not clear, which status or statuses are used by default in the above case.
for issue in rm.issue.filter(project_id='portal', status_id='*'):
worked as approriate for me.

@andrius-momzyakov andrius-momzyakov changed the title Filter operation with no status_id parameter not found closed issues. Filter operation with no status_id parameter set found no closed issues. Jun 27, 2016
@maxtepkeev maxtepkeev self-assigned this Jun 27, 2016
Copy link

@maxtepkeev maxtepkeev commented Jun 27, 2016

Yeah I know, actually python-redmine just uses default Redmine API behaviour, and it returns only open issues by default. But I agree that docs need a bit of clarification. Thanks for raising this issue.

Copy link

@maxtepkeev maxtepkeev commented Mar 12, 2017

This information was added to the new docs that will be available together with v2.0.0 in the end of March.

@maxtepkeev maxtepkeev closed this Mar 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants