Bug 1025595 - RFE - Give Product entities a base list of tags that are commonly used rather than under the bucket "Common" Product Entity
Summary: RFE - Give Product entities a base list of tags that are commonly used rather...
Keywords:
Status: CLOSED DUPLICATE of bug 817450
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: pressgang-ccms-dev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-01 03:45 UTC by Jared MORGAN
Modified: 2015-08-10 01:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-11-03 22:38:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Jared MORGAN 2013-11-01 03:45:41 UTC
Background:

I'm currently going through my docs and adding metadata to the topics. I made the mistake of moving the "Concept", "Task", and "Reference" tags under the RHJP project,  which removed them from the Common project.

Issue:

If I wanted to specify that these tags are present in more than one project, I have to add all 30 product entities to the tag. 

All this so I can have all the tags relevant to my product sorted under my product entity.

RHJP > Topic Types > Concept|Task|Reference 

instead of 

Common > Huge list of irrelevant stuff > list of slightly less irrelevant stuff > Concept|Task|Reference 

If you are doing a lot of topic metadata rework, this get really tedious, really quickly.

I understand that these common tags are used in most projects, and the Topic Types in particular are commonly used everywhere. 

Enhancement:

Why not have (at a minimum) the Topic Types sort under new and existing projects by default and if a project decides they don't want the full list of tags, they can remove the tags that don't apply to their product.

Comment 1 Lee Newson 2013-11-03 22:38:34 UTC

*** This bug has been marked as a duplicate of bug 817450 ***


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