Bug 100996 – UI for setting permissions on categories is missing

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 100996 - UI for setting permissions on categories is missing

Summary:	UI for setting permissions on categories is missing

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Enterprise CMS
Classification:	Retired
Component:	other (Show other bugs)
Sub Component:
Version:	nightly
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Archit Shah
QA Contact:	Jon Orris
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	98546
	Show dependency tree / graph

Reported:	2003-07-28 09:07 EDT by Daniel Berrange
Modified:	2007-04-18 12:56 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-10-10 16:52:00 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Berrange 2003-07-28 09:07:06 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.9 (X11; Linux i686; U;) Gecko/20030314

Description of problem:
The categories tab in the content section admin pages needs the controls for
setting permissions on categories. This should have been part of the URL based
category browser merges, but appears to be missing. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Go into a content section
2. Go to the categories tab


Actual Results:  There is no UI to view / change permissions

Expected Results:  There is UI to view / change permissions

Additional info:

Comment 1 Richard Li 2003-07-28 09:10:11 EDT

I thought ashah wrote some of this.

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