Bug 948189

Summary: Add statistics on reuse and parent content specs.
Product: [Community] PressGang CCMS Reporter: Eva Kopalova <ekopalov>
Component: CCMS-CoreAssignee: pressgang-ccms-dev
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: lnewson, mcaspers
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-09 05:23:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 831910    
Bug Blocks:    

Description Eva Kopalova 2013-04-04 09:20:40 UTC
I have noticed there was a button in the web gui that provided the information on which content specifications are using the current topic. Could we have it back, please?

Also, it would be nice to see general statistics on topic re-use (how many topics are re-used, how many topics are re-used once/twice, etc.).

Comment 1 Matthew Casperson 2013-04-07 23:04:31 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=947968 for details on how to search for content specs that include a topic. The button will be readded once the content specs are converted into proper database entities, and we have hard links between a content spec and a topic.

Comment 2 Matthew Casperson 2013-04-08 07:43:39 UTC
The following report can be used to see what topics are reused between content specs: http://skynet.usersys.redhat.com:8080/birt/frameset?__report=General/Topic_Reuse.rptdesign

Enter a content spec ID, and the report will show you the topics from that content spec, and any other content specs they are used in.

Comment 4 Lee Newson 2013-10-09 05:23:48 UTC
Moving this bug to CLOSED CURRENT_RELEASE to clean up old bugs that were QA'd
by the PressGang team but not by the original reporter. If the bug is still present then please re-open the bug.