https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292019-09-19T01:46:40ZRedmineRedmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=937962019-09-19T01:46:40ZGo MAEDA
<ul></ul><p>You can get users with any status by adding 'status=' parameter.</p>
<pre>
curl --user admin:password 'http://redmine.example.com/users.json?status='
</pre> Redmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=938112019-09-19T12:11:01ZMartin von Wittich
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>Go MAEDA wrote:</p>
<blockquote>
<p>You can get users with any status by adding 'status=' parameter.</p>
</blockquote>
<p>That does exactly what I wanted, thanks! I've updated the wiki accordingly.</p> Redmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=938142019-09-19T15:38:15ZMartin von Wittich
<ul></ul><p>Hm, there is one other issue I've stumbled over - <code>users.json?name=foobar&status=</code> won't return the status of the matched users. I either have to query the statuses separately (<code>users.json?name=foobar&status=1</code> and so on) so I know that all matched users have the status I just queried, or I have to query each returned user separately with <code>users/<id>.json</code> to get the user's status. Is that intentional, or could a <code>status</code> field be added to <code>users.:format</code>?</p> Redmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=1010292021-02-20T16:44:16ZYar n
<ul></ul><p>This is so extremly not obvious. <br />Is it possible to update documentation to point to that feature?</p> Redmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=1125112024-01-25T15:39:54ZMarius BÄ‚LTEANU
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/40099">Defect #40099</a>: User api filtering by status=* broke on upgrade from 5.0 to 5.1</i> added</li></ul> Redmine - Feature #32090: REST API: users: add support for status=*https://www.redmine.org/issues/32090?journal_id=1125132024-01-25T15:43:43ZMarius BÄ‚LTEANU
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul>The behaviour changed as follow:
<ul>
<li>Redmine <= 5.0.*: you can use <code>status=</code> to get all users from API</li>
<li>Redmine 5.1.0 and 5.1.1: you can only use <code>users.json?f[]=status_id&op[status_id]==&v[status_id][]=1&v[status_id][]=2&v[status_id][]=3</code> to get all users because of <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: User api filtering by status=* broke on upgrade from 5.0 to 5.1 (Closed)" href="https://www.redmine.org/issues/40099">#40099</a>.</li>
<li>Redmine >= 5.1.2: you can use <code>status=</code> which is now deprecated in favour of <code>status=*</code> or the long syntax</li>
<li>Redmine 6.0: you can only use <code>status=*</code> or the long syntax</li>
</ul>