Bug 1376322 - Add hook in Bugzilla::WebService::Bug::_bug_to_hash
Summary: Add hook in Bugzilla::WebService::Bug::_bug_to_hash
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified with 1 vote vote
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Jeff Fearn 🐞
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 05:34 UTC by Matt Tyson 🤬
Modified: 2022-11-01 01:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-01 01:16:37 UTC


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.