Bug 87596 - Can't categorize CIs; lack permission
Summary: Can't categorize CIs; lack permission
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Justin Ross
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 88926
TreeView+ depends on / blocked
 
Reported: 2003-03-29 20:06 UTC by Jon Orris
Modified: 2007-04-18 16:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-06-03 21:24:37 UTC
Embargoed:


Attachments (Terms of Use)

Description Jon Orris 2003-03-29 20:06:48 UTC
@29175 Postgres
Description of problem:
The author of a content item cannot categorize it. Get a message saying: 
'Need categorize items privilege on that category'

Several CMS tests assign items to categories & test published article
categorization.

Comment 1 Justin Ross 2003-05-27 15:37:22 UTC
I need some guidance on this one.  The category permission checks on tip are the
same as those that existed when I started making UI changes.

So, what is the *expected* behavior?  Should an item author automatically get
the categorize-items privilege?  Scott, I added you since you mentioned
something about changes to permissions in categorization.

Comment 2 Scott Seago 2003-05-27 15:45:26 UTC
I _think_ the right thing here would be to grant the author the "Categorize
items"  privilege. I don't know what the exact use case for this is, but I
expect it would be something like "We have 100 authors, but only some of them
have the privilege to categorize items -- items authored by those other authors
will have to be categorized at the approval step" or something like that. In any
case, if granting the author (or the author's role) that privilege solves the
problem, then it sounds like the system is working as intended.

Comment 3 Justin Ross 2003-06-03 19:29:05 UTC
Fixed in perforce 31973 by adding the categorize_items privilege to the Author
role in CMS's enterprise.init.in.


Note You need to log in before you can comment on or make changes to this bug.