Make change-queue generate the OST report

Description

Since the change-queue has all the information needed for this, we can make it generate the OST report.

Activity

Show:

Barak Korren October 15, 2018 at 3:32 PM

not sure, the weekly report now exists separately from the per-issue reporting to developers. It may or may not be needed once we automate the per-issue reporting.

We'll need to revisit that once is done.

Dafna Ron October 15, 2018 at 1:26 PM

do we need this once OVIRT‌-1447 will be implemented?

Barak Korren August 1, 2018 at 11:54 AM

yeah, I think it was created back when we were maintaining a spreadsheet in googledocs.

Dafna Ron August 1, 2018 at 8:02 AM

I think things changed and this ticket may not be relevant any more?

Barak Korren October 17, 2017 at 2:56 PM

I don't think having Jira tickets would have any considerable benefit over having email messages, both thecniques would require you to manually aggregate an analyse messages...

Putting the information in some kind of a database or a spreadsheet would provide far better analysis and aggregation tools.

Here is a somewhat hack-ish idea - setup a new fake mail account which is a member of infra, then have something like ifttt monitor emails reaching it and convert them into lines in a google spreadsheet.

Details

Assignee

Reporter

Components

Priority

Created June 21, 2017 at 7:34 AM
Updated October 15, 2018 at 3:32 PM