RoR Enterprise: Reporting custom context issue 6.8.0 1.19.4

Hi,

We now upgraded to 1.19.4 on Kibana and Elasticsearch 6.8.0.
If we go into a custom context and generate a report there, it ends up in the reporting of the default kibana

Config:

  - name: "IT2line custom kibana"
    indices: ["kibana_it2ndline", ".reportingkibana_it2ndline-*", "longlistofdataindices"]
    kibana_index: "kibana_it2ndline"
    kibana_access: rw
    kibana_hide_apps: ["monitoring", "maps", "uptime", "timelion", "readonlyrest_kbn", "canvas", "apm", "infra:home", "infra:logs", "kibana:dev_tools", "kibana:management"]
    groups: ["IT2ndline_custom"]

  users:
  - username: ronald
    auth_key_sha256: xxx
    groups: ["IT2ndline_custom"]

If I generate the report, it ends up in:
.reporting-2020.04.05
While running the report today on 2020.04.07?

I see no index
.reportingkibana_it2ndline-*
being created.

If I check the audit log I see the following:

Time req_method action indices type path user final_state
April 7th 2020, 15:45:44.000 POST indices:data/read/search .kibana SearchRequest /.kibana/_search ronald INDEX NOT EXIST
April 7th 2020, 15:45:44.000 POST indices:data/write/index .kibana IndexRequest /.kibana/doc/config:6.8.0/_create ronald FORBIDDEN
April 7th 2020, 15:45:44.000 GET indices:data/read/get .kibana GetRequest /.kibana/doc/config:6.8.0 ronald INDEX NOT EXIST
April 7th 2020, 15:45:44.000 POST indices:data/write/index .kibana IndexRequest /.kibana/doc/config:6.8.0/_create ronald FORBIDDEN
April 7th 2020, 15:45:43.000 POST indices:data/read/search .kibana SearchRequest /.kibana/_search ronald INDEX NOT EXIST
April 7th 2020, 15:45:43.000 GET indices:data/read/get .kibana GetRequest /.kibana/doc/config:6.8.0 ronald INDEX NOT EXIST

If you log in with a user that has access to management on the default Kibana, the report is shown there and can be downloaded by that user.
But in the management of the custom Kibana it is not shown.

If you need any more information please let me know how I can help.

OK This is a regression. Will kill it tomorrow.

OK This is fixed, I will send you an updated pre-release via PM here in the forum.