Bug 1318661

Summary:	Feature request: 'Invalidate' a bugzilla comment.
Product:	[Community] Bugzilla	Reporter:	Ravishankar N <ravishankar>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED DEFERRED	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	huiwang, iamanikamalhotra, jmcdonal, mtahir, qgong
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:	2016-04-06 00:32:02 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:

Description Ravishankar N 2016-03-17 13:13:58 UTC

Description of problem:

It so happens that when 'ctrl-tabbing' through multiple BZs on your browser, you inadvertently end up typing a comment in the wrong BZ, only to realize it later and add another comment to the tune of "Please ignore comment #XX", it was meant for another BZ". A person reading the BZ from the beginning might not realise it until he has gone through the entire comment. One might argue that an incorrect comment might immediately be recognisable as out of context from the BZ's point of view, but I have come across many instances where that isn't the case. And to be honest, yours truly has also many times ended up posting comments meant for one BZ in another.

What I am requesting is some sort of a 'Invalid Comment' check-box (like the one we have for private comments) which greys out or strikes through whatever is typed in the comment so that we have some sort of `quick visual indication` to just skip reading it.

P.S: Filing it under 'Bugzilla General' as I'm unsure of the component (and version).

Comment 1 Muhammad Tahir 2016-04-06 00:32:02 UTC

Hi, this functionality is not a priority for us and will not get resources
allocated to it. If you really want this feature you might have more luck
upstream.

Comment 2 Ravishankar N 2016-04-06 04:14:12 UTC

(In reply to Muhammad Tahir from comment #1)
> Hi, this functionality is not a priority for us and will not get resources
> allocated to it. If you really want this feature you might have more luck
> upstream.

Hi,
Okay, just for confirmation, is https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla the upstream version where I can raise a bug?

Comment 3 Muhammad Tahir 2016-04-06 04:39:11 UTC

(In reply to Ravishankar N from comment #2)
> Hi,
> Okay, just for confirmation, is
> https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla the upstream
> version where I can raise a bug?

Yes

Comment 4 Ravishankar N 2016-04-11 17:35:25 UTC

Tahir,

So I raised a bug @https://bugzilla.mozilla.org/show_bug.cgi?id=1263573 and apparently there is a 'comment tagging' feature already present upstream. Tagging a comment as 'obsolete' seems to do the trick.

I hope you can prioritize back-porting this to RH bugzilla for a subsequent release. It would really be a useful improvement.