| 1 |
On 20/03/2018 06:05, Paweł Hajdan, Jr. wrote: |
| 2 |
> On 19/03/2018 21:33, Alec Warner wrote: |
| 3 |
>> I'd avoid the REST API here. If you want this data; I'd consider filing a |
| 4 |
>> bug. Infra can do stuff like run nightly reports for this information and |
| 5 |
>> hang them off of endpoints you can access. |
| 6 |
>> This works well for public bugs; and not well for private ones. |
| 7 |
> |
| 8 |
> Luckily, I'm not that concerned with private bugs. |
| 9 |
> |
| 10 |
> Would it only collect data going forward, or does this method also |
| 11 |
> support historical backfill? |
| 12 |
> |
| 13 |
>>> I've done something like this before with Perl bugs[1], but again, very |
| 14 |
>>> painful, slow and time consuming. |
| 15 |
> |
| 16 |
> Ah, that looks like lots of stats. |
| 17 |
> |
| 18 |
> I'm mostly interested in how many bugs were open for given assignee for |
| 19 |
> each point in time. |
| 20 |
> |
| 21 |
> If you still have scripts that generated these reports and they could be |
| 22 |
> useful to compute the above, I could be interested. |
| 23 |
|
| 24 |
Just checking back here - what would be the best way to graph number of |
| 25 |
bugs with given assignee, preferably with historical backfill? |
| 26 |
|
| 27 |
I'm not necessarily looking for something ready to use right away. If |
| 28 |
there's some work to be done or code to implement, I may be willing to |
| 29 |
do so. |
| 30 |
|
| 31 |
Paweł |
Archives