Apparently it's a behavior of the plugin itself.
Per the documentation on https://plugins.jenkins.io/role-strategy/:
Global roles apply to any item in Jenkins and override anything you specify in the Project Roles. That is, when you give a role the right to Job-Read in the Global Roles, then this role is allowed to read all Jobs, no matter what you specify in the Project Roles.
But I think this behavior strange, since the projects are already configured. If we delete the global rule and create it with new permissions and with the same name, it ends up having the expected behavior.
Apparently it's a behavior of the plugin itself.
Per the documentation on https://plugins.jenkins.io/role-strategy/:
But I think this behavior strange, since the projects are already configured. If we delete the global rule and create it with new permissions and with the same name, it ends up having the expected behavior.