You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when trying to filter time entries based on user_id, it seems the option is ignored. Now, unlike my previous issue, it is important to say that user_id filter DOES NOT work with the REST API of my ChiliProject, either.
The reason why I am asking this anyway is that the python-redmine docs say that this filter exists, but the Redmine REST API documentation does not mention it.
So, does it work with Redmine? If yes, is there a way to make it work with ChiliProject or is that project too long dead?
Many thanks.
The text was updated successfully, but these errors were encountered:
Python-Redmine docs indeed have some filters that are not mentioned on Redmine REST API docs because Redmine docs are not really up to date. When I was developing python-redmine I was looking at the Redmine sources mainly to see what filtering options are available. That is why I recommend you to stick with python-redmine docs and not with the Redmine REST API docs.
Answering your question - yes, user_id filter for time entries for Redmine does really work, and yes Redmine REST API docs doesn't mention it, because they are not really up to date. No, it doesn't work with ChiliProject and I don't think it is possible to make it work without modifying ChiliProject source code.
Hi again,
when trying to filter time entries based on user_id, it seems the option is ignored. Now, unlike my previous issue, it is important to say that user_id filter DOES NOT work with the REST API of my ChiliProject, either.
The reason why I am asking this anyway is that the python-redmine docs say that this filter exists, but the Redmine REST API documentation does not mention it.
So, does it work with Redmine? If yes, is there a way to make it work with ChiliProject or is that project too long dead?
Many thanks.
The text was updated successfully, but these errors were encountered: