Bug 773761

Summary: "Delete" permission is not as useful as "Create, Read, Modify"
Product: Red Hat Satellite Reporter: Jeff Weiss <jweiss>
Component: WebUIAssignee: Partha Aji <paji>
Status: CLOSED UPSTREAM QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: dajohnso, mmccune, sghai
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-19 18:13:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeff Weiss 2012-01-12 20:05:39 UTC
Description of problem:
<jweiss-pto> i would have expected:  R, RU, CRU, CRUD.  It appears there is R,
             RD, RU, CRUD  [17:50]
<jweiss-pto> i would have thought CRU is way more useful than RD  [17:51]
<jweiss-pto> who would ever get the "delete" role?

I have a hard time thinking of a use case for the delete role - some kind of grim reaper user who only deletes things?

If there's some use case for Delete, that is fine, but still think we should add "CRU" - Create Read Update (or Modify, as we call it in the UI).  Otherwise there is no way to give a user permission to create, without giving him full admin permission.

Version-Release number of selected component (if applicable):
katello-0.1.175-1.git.19.7ffe744.el6.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Mike McCune 2012-01-20 20:22:33 UTC
moving to V 1.1, not enough time left to revamp how they are worded now.

Comment 3 Partha Aji 2013-01-22 20:06:15 UTC
create is now called administer 
update is now called modify


Those changes happened around 1.1

Comment 4 Mike McCune 2013-09-19 18:13:48 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.