Bug 844241

Summary:	gluster product imports have bad status
Product:	[Community] Bugzilla	Reporter:	yawei Li <yawli>
Component:	Bug Import/Export/Moving	Assignee:	Simon Green <sgreen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.2	CC:	aigao, cward, ebaak
Target Milestone:	4.2-5
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.2.4-6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-15 03:53:39 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 yawei Li 2012-07-30 05:16:44 UTC

It is from cward's email:

Seems Gluster product bugs are being imported with their activity
history showing

Status - Added: RESOLVED

But RESOLVED isn't actually a valid status... and bug is in CLOSED
status now.

https://bugzilla.redhat.com/show_activity.cgi?id=761772

The activity entries should be (have been) updated to say
'CLOSED', on import to Bugzilla, no? Or was this expected?

Also, since i'm finding quite a lot of errors of this sort,
does the bz team accept requests to fix this type of data import
error retroactively in the production DB? Or in all cases the
plan is to leave it to ETL?

-Chris

Comment 2 Simon Green 2012-08-22 06:11:56 UTC

(In reply to comment #0)
> https://bugzilla.redhat.com/show_activity.cgi?id=761772
> 
> The activity entries should be (have been) updated to say
> 'CLOSED', on import to Bugzilla, no? Or was this expected?

Should have, but weren't. This will be fixed once this bug goes live.

> Also, since i'm finding quite a lot of errors of this sort,
> does the bz team accept requests to fix this type of data import
> error retroactively in the production DB? Or in all cases the
> plan is to leave it to ETL?

The Red Hat Bugzilla team will consider them on a case by case basis. The main issues that we will consider is 1) is it easy to fix?, 2) can we accurately fix it? 3) what is the effect of not fixing it? 4) what are the advantages in fixing it?

Comment 3 Chris Ward 2012-08-22 07:46:43 UTC

Thanks guys!