Actions
Bug #10492
closed
validate permission name should be unique and not scoped by resource_type
Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Updated by Joseph Magen over 9 years ago
- Subject changed from role.add_permission doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values to role.add_permissions doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2377 added
- Pull request deleted (
)
Updated by Joseph Magen over 9 years ago
- Subject changed from role.add_permissions doesn't account for when multiple permission entries exist in the DB with the same permission name but different resource_type values to validate permission name should be unique and not scoped by resource_type
Updated by
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 35
Updated by Joseph Magen over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 04ad52f78f83954bec062a48a0ee3cd7d35bb9dd.
Actions