Bug 168964

Summary:	Bugzilla should regularly attempt to update IT scores when they are -1
Product:	[Community] Bugzilla	Reporter:	Suzanne Hillman <shillman>
Component:	Bugzilla General	Assignee:	David Lawrence <dkl>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.18	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	2.18	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-04-10 19:30:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Suzanne Hillman 2005-09-21 18:41:41 UTC

Description of problem:
Lots of IT scores are left at -1 if IT can't update BZ because it's down. I've
also entered a bug against IT, as it should try again later. However, it would
also be good on Bugzilla's side, since only bugzilla can know what bugs have -1
IT scores, to regularly try to update those scores. Perhaps weekly?

Comment 1 David Lawrence 2006-04-08 18:04:58 UTC

Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 2 Suzanne Hillman 2006-04-10 19:27:43 UTC

I no longer do bug triage, so have no direct exposure with recently entered
bugs, but a quick search where IssueTracker contained or was equal to -1 showed
no -1 issue tracker values, so this likely is fixed. No real way to be sure,
beyond that.

Comment 3 David Lawrence 2006-04-10 19:30:44 UTC

Actually Bugzilla will now do a remote call to IT to get a score before it will
set it to -1 so you are right.