We're updating the issue view to help you get more done. 

Permissions for newly created metadata elements not set

Description

When creating new metadata elements privileges are not set for existing roles until the role is explicitly saved in the UI. Until privs are set by save, the default prig is used; when the default is restrictive users can get very very confused.

We should explicitly set privs for roles when an element is created.

Environment

None

Assignee

User known

Reporter

User known

Labels

None

Fix versions

Affects versions

Priority

Major
Configure