created_at:{operator} filters do not work when formIDs filter is specified

[wzup]

If formIDs array is, say about 100 items, created_at:{operator} filters are not applied (docs).

Example.
If I remove formIDs option, oh my goodness, the API suddenly start working and returns as expected with created_at: applied.
If I specify formIDs, like in an example below, created_at:operators are not applied and number of returned submissions is as many as limit option says.

jf.getSubmissions({
        offset: '0',
        limit : '100',
        filter: {
            "created_at:gte": moment().set({hour: 0, minutes: 0, seconds: 0}).format('YYYY-MM-DD HH:mm:ss'),
            "created_at:lt": moment().add(1, 'day').set({hour: 0, minutes: 0, seconds: 0}).format('YYYY-MM-DD HH:mm:ss'),
            formIDs: ["formID1", "formID2", ...say 100 items]
        }
})

When may we expect the fix?
As always: "sorry, we cannot fix it quickly"?

[hasansoydabas]

@selengenc Could you please check this with plain cURL and jotform-api-nodejs just to be sure that isn't related with the library?

[selengenc]

Hi,
We checked this request with your form ids. And, we increased size of character the filter parameter. You can make a request with more than 100 form ids.

You could request this url;

• Get submission with this FormIDs (FormID1, FormID2,....)
  http://api.jotform.com/user/submissions?
  apiKey={apiKey}
  &filter={"created_at:gt":"2013-01-01 00:00:00",
  "formIDs":["FormID1","FormID2","FormID3"]}
  &limit=1000
  &orderby=created_at
• Get submission with not this FormIDs (FormID1, FormID2,....)
  http://api.jotform.com/user/submissions?
  apiKey={apiKey}
  &filter={"created_at:gt":"2013-01-01 00:00:00",
  "form_id:ne":["FormID1","FormID2","FormID3"]}
  &limit=1000
  &orderby=created_at

[wzup]

Very nice.
When we found other approach how to overcome Jotform faults on our side you finally deliver a solution. Thank you though.

@selengenc @hasansoydabas
Now could you please be so kind and add a formId filter for GET /user/forms endpoint?
I have created a separate issue for it #12