Bug 1376322

Summary:	Add hook in Bugzilla::WebService::Bug::_bug_to_hash
Product:	[Community] Bugzilla	Reporter:	Matt Tyson 🤬 <mtyson>
Component:	Bugzilla General	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jeff Fearn 🐞 <jfearn>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	dylan, huiwang, qgong
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-11-01 01:16:37 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 Matt Tyson 🤬 2016-09-15 05:34:16 UTC

The _bug_to_hash function is commonly used to add new fields to the Bug.get call.

We have several such extensions already cluttering up this function.

I'd say it's time we pushed these out into their respective extensions and called into them with hooks.

Comment 1 Dylan Hardison 2016-09-19 16:51:53 UTC

extension hooks are quite expensive, I would recommend having a 'bugs_to_hash' hook that took an arrayref of bugs and performed whatever operation,
so that if you have 10,000 bugs you don't have to call the extension 10,000 times. we'd accept that solution upstream.

Comment 3 Jeff Fearn 🐞 2022-10-21 02:43:10 UTC

On QA server.

1: Run Bug.get on a bug with external trackers and a pool.

Returned data includes, ETs, pool data, and other custom values.

Passed.

Comment 4 Jeff Fearn 🐞 2022-10-27 02:55:39 UTC

The fix for this issue has been deployed to the stage server for a short period of public testing.

https://bugzilla.stage.redhat.com

Comment 5 Jeff Fearn 🐞 2022-11-01 01:16:37 UTC

This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug.