Bug 1281880

Summary: Github as external bug tracker
Product: [Community] Bugzilla Reporter: Jason Tibbitts <j>
Component: Bugzilla GeneralAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: mtahir, qgong, ville.skytta
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-09-01 09:35:03 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 Jason Tibbitts 2015-11-13 17:04:43 UTC 
I was surprised to see that I can't reference github as an external tracker, and I did some searching here and didn't seen an open ticket, so...  Please consider adding some way to reference a github issue as an external bug.

I suppose with a naive implementation each github project would have to be added individually, which obviously wouldn't scale.  But it should be possible to include the project name in the "Bug ID" that bugzilla would use, which would give you enough of a unique ID to find the issue.  For example, "SpamExperts/pyzor/38", or just take the whole URL and parse it.  There's enough information there to get down to https://api.github.com/repos/SpamExperts/pyzor/issues/38 for the json you need to determine the ticket state.
Comment 1 Jeff Fearn 🐞 2016-09-01 09:35:03 UTC 
Github is there now, usage is "SpamExperts/pyzor/38"
Comment 2 Jason Tibbitts 2016-09-01 14:13:47 UTC 
This is great, thanks!
Comment 3 Ville Skyttä 2016-09-07 07:05:08 UTC 
FWIW I just tried to use this feature in bug 1373295, but the ccache/ccache/129 usage resulted in a broken link. Had to use ccache/ccache/issues/129.