Project

General

Profile

Actions

Bug #10492

closed

validate permission name should be unique and not scoped by resource_type

Added by Joseph Magen about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Users, Roles and Permissions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:
Actions #1

Updated by Joseph Magen about 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
Actions #2

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2377 added
  • Pull request deleted ()
Actions #3

Updated by Joseph Magen about 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
Actions #4

Updated by Bryan Kearney about 9 years ago

  • Bugzilla link set to 1221343
Actions #5

Updated by Dominic Cleal about 9 years ago

  • translation missing: en.field_release set to 35
Actions #6

Updated by Joseph Magen about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF