Kibana permissions - different behavior between read and custom privileges

I recently migrated from elastic cloud to elastic cloud on kubernetes. In order to migrate, I restored a snapshot with all the users and roles. I wanted to make a change to a custom role I created to allow a user to create CSV reports. When I changed the Kibana permissions from read to all to the discover feature, the user stopped to have access to the entire Analytics.

I tested it a bit and I can see that creating a custom role with All or Read kibana privileges gives the user access to discover and the other features, but if I configure a Custom Kibana privilege with all read access (basically doing the same thing as Read privilege), the user does not have access to discover. Is it a bug or am I missing something ?

TLDR : This gives access to discover :

But this does not :

Even though they are supposed to give the same access

For some reason, xpack.reporting.roles.enabled was set to false. Enabling it solved the issue