Tailor Permissions get grouped by name and not by parent navigation

[sqwk]

I have multiple tailor items named Tag. These are all grouped together in the permissions backend, even though they have different uuid, handle and navigation.parent options set.

name: Tag

navigation:
    label: Tags
    parent: Blog\Article

name: Tag

navigation:
    label: Tags
    parent: Foo\Bar

Shouldn't the permission be grouped by the name of the parent item?

[daftspunk]

This is an interesting use case.

We may need to add permissionCode to allow multiple blueprints to share a single permission. Would it solve the problem for you?

[sqwk]

I don't so much need the blueprints to share a single permission, I just need to be able to identify them. At the moment, one has to give a user the permission, log in as them and check if the one selected is the right one. In the screenshotted example it would be much more obvious if tags are listed under the heading Article and Bar respectively and not both under Tag.

[daftspunk]

Ok, based on this:

• add the ability to set a custom code and label for the Tailor permissions