rest api: filters ignored for computing the "total" in /jobs or /jobs/details

[mimbert]

A request such as GET /jobs?user=<USERNAME> or GET /jobs/details?user=<USERNAME> will correctly return only the jobs pertaining to the user, but in the response, the total field ignores the filter and is the total of the GET /jobs / GET /jobs/details without the ?user=<USERNAME> filter.

This makes handling pagination of responses a bit whacky, i.e: don't use the total to track the last page, instead, try to read pages until it gets an empty page. Maybe it was intended like that? or is that a bug?