Bug 115946 - Breadcrumb trail when creating JSP templates should take user to 'Content types' tab instead of 'Browse'
Summary: Breadcrumb trail when creating JSP templates should take user to 'Content typ...
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: ui   
(Show other bugs)
Version: nightly
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Scott Seago
QA Contact: Jon Orris
Depends On:
TreeView+ depends on / blocked
Reported: 2004-02-17 11:15 UTC by Daniel Berrange
Modified: 2007-04-18 17:03 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-02 17:47:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Daniel Berrange 2004-02-17 11:15:34 UTC
Description of problem:
When creating a JSP template for a content type, the breadcrumb trail
has a link back to the content section. When clicking this link, you
are taken back to the 'Browse' tab in the content section. It would
make more sense to be taken back to the 'Content types' tab. The
contnet type select on this tab should be the one that the admin was
working with when creating the template.

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

How reproducible:

Steps to Reproduce:
1. Go to /ccm/contnet/admin/
2. Go to 'Content types'
3. Select 'multipart article'
4. Create a new template
5. Click on breadcrumb link for 'Content section: content'

Actual results:
Taken to 'browse' tab in content section admin

Expected results:
Taken to 'content types' tab with 'Multipart article' selected.

Additional info:

Comment 1 Scott Seago 2004-02-19 01:06:37 UTC
fixed @40543

Comment 2 David Lawrence 2006-07-18 02:47:25 UTC
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future.
Moving to ON_QA.

Comment 3 Daniel Berrange 2006-09-02 17:47:35 UTC
Closing old tickets

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