Bug 889223

Summary:	Installation Guide shipped with Bug Links = On
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Stephen Gordon <sgordon>
Component:	Documentation	Assignee:	Cheryn Tan <chetan>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, chetan, dyasny, gklein, rlandman, thildred, yeylon
Target Milestone:	---	Keywords:	Documentation
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-09 02:29:49 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:

Description Stephen Gordon 2012-12-20 14:48:45 UTC

Description of problem:

The 3.1 Installation Guide shipped with Bug Links = On. Unfortunately as Dan Yasny has pointed out to me while some restrictions on RHEV-M bugzilla were raised in 3.1 customers still do not have the ability to raise bugs.

Obviously this means that in the short term the report a bug links need to be turned off, and a discussion had about whether they can be customized on a more granular basis (see Bug # 885752, Bug # 885689).

In addition to this though the Feedback.xml section used for all RHEV guides also directs customers to Bugzilla. As a result the chances of us receiving feedback via any mechanism other than direct email to the author (for authors that actually list their email on the cover page, not all do) is very low.

Comment 3 Stephen Gordon 2012-12-20 15:28:18 UTC

I have the changes required to do this in my local workspace ready for commit if required.

Comment 4 Stephen Gordon 2012-12-20 15:30:20 UTC

(In reply to comment #3)
> I have the changes required to do this in my local workspace ready for
> commit if required.

To be clear, "doing this" in this case would mean removing the bug links - we would still need a discussion about what/how to handle the feedback section for all guides.

Comment 5 Stephen Gordon 2012-12-20 15:58:12 UTC

Branched the content spec for 3.2 (where this change will be applied unless it goes z-stream in which case as above I have a commit ready), new ID is 12875.

Comment 6 Cheryn Tan 2013-05-09 02:29:49 UTC

Not quite a duplicate, but will be addressed as part of bug 885689

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