1285824 - Get shields.io to support bugzilla

Status: NEW

(Bugzilla :: Bugzilla-General, enhancement, P3)

Description

[Dylan Hardison [:dylan] (he/him)]

I'd like to be able to use shields.io for:
- The number of unresolved bugs in a product/component
- a particular bug's status

We could do this purely in bugzilla by redirecting to custom shields.io
urls, but contributing a patch to that would be better.

Comment 1

[Dylan Hardison [:dylan] (he/him)]

Actually, looking at how readthedocs supports this, we would be right to write our own endpoint that makes an HTTP request to sheids.io. That seems pretty easy. We'll want to have an option to disable support for this, and have it disabled by default.

Comment 2

[Sebastin Santy [:seban]]

Hi Dylan,

Wanted to take up this bug. I can't completely understand your second point of the first comment (Like where will it be displayed, like on a github PR?). According to what I interpret, all the metrics will be calculated and passed into the image url of shields.io. Am I going right?

Comment 3

[Dylan Hardison [:dylan] (he/him)]

(In reply to Sebastin Santy [:seban] from comment #2)
> Hi Dylan,
> 
> Wanted to take up this bug. I can't completely understand your second point
> of the first comment (Like where will it be displayed, like on a github
> PR?). According to what I interpret, all the metrics will be calculated and
> passed into the image url of shields.io. Am I going right?

What readthedocs.org does is make the HTTP request to shields.io and returns the response content to the browser. 

So https://bugzilla.mysite.org/badge/bugs/TestProduct
would do is my $resp = LWP::UserAgent->new->get("https://img.shields.io/badge/bugs-312-blue.svg");
and then returns $resp->body to the client.

this would require adding a badge.cgi (which would be similar to rest.cgi)
and some thought to security. I think badge.cgi should operate as the 'nobody' user and not return any info about bugs that are non-public, for instance.

Comment 4

[Sebastin Santy [:seban]]

Thanks for the help!

(In reply to Dylan William Hardison [:dylan] from comment #0)
> I'd like to be able to use shields.io for:
> - The number of unresolved bugs in a product/component
> - a particular bug's status

Where will we display the particular bug's status. Or like we can give a link within the show_bug page itself for the badge, so that people can use them wherever they want. If so, what/where will be the use of showing the (status of bug) badges.

Comment 5

[Firefox Bug Husbandry Bot]

Removing good-first-bug keyword because team does not have bandwidth to mentor at the moment.