14
edits
Compatibility/Meetings/Sync w Honza: Difference between revisions
Jump to navigation
Jump to search
Compatibility/Meetings/Sync w Honza (view source)
Revision as of 13:00, 16 April 2024
, 16 April 2024sync 16th of April
(March 19) |
(sync 16th of April) |
||
| Line 1: | Line 1: | ||
== April 16 == | |||
=== New dashboard system (Honza) === | |||
Honza: I've shared the link, I am curios if you can login. It takes some time to load. This is the first version. | |||
The second link shows a graph. It is a submission count, shows the reports submitted per day. +- 2000 per day. As you can see, the numbers are low at first, due to the experiment period. Then it jumps, since more users have had this new reporting system. | |||
As you can see, a lot of data is present. From the overview dashboard, we can see the number of reports received by site, by day, with comment, without comment, based on OS, etc. | |||
We can also see that if an issue is currently known or not. | |||
Paul: How does QA fits in this new dashboard? We will have a shorter list that QA can test and try to reproduce. Not sure how we should tackle this, with what to start. Triaging 1000s of issues per day is not really feasable. | |||
Honza: Right. So we need features that will help QA in their triaging process, so that they can focus on the valid, reproducible issues. The first approach is to see what domain has the most reports. From the data shown, the first indication is that youtube has the most issue, so we should focus there. Sorting those issues somehow is another priority. | |||
Paul: Maybe a keyword in comments, a root cause, would help. | |||
Honza: Right, we should look at the most promising comments. You mentioned the kanban board with top most issues. | |||
Paul: We can somehow filter that most of the people reporting the same incomplete issue, raises the urgency of checking that issue. | |||
Honza: That is the future, lower quality, high number of reprots. So that is our focus now, to somehome implement some feature to make small progress. | |||
Paul: Maybe the ability to search by comments and be ranked based on the information provided. | |||
Honza: I agree but this more for statistics to figure it out where there could be more potential issues. | |||
Paul: We could schedule a meeting and brainstorm ideas on how to make it better, to extract the most info from the reports we are receving. | |||
Raul: Will the Ml-bot still be active? | |||
Honza: Sure. | |||
Paul: We will have as mentioned, an internal meeting, and we will present the brainstorming ideas to the team regarding the features that would be useful. | |||
Honza: Sure, both triaging and work tracking should be supported. How much time do you thing you need? | |||
Paul: Most likley this week. | |||
Raul: Let's say we have everything in place, what if we get 200 valid reports a day because most likely we won't be able to keep up. | |||
Honza: We don't know exactly yet, we will have to check how it goes and decide then. We will identify the bottleneck issues, maybe we will see that we are received less valid reports, and uppermanagement will need to take action towards this. | |||
== March 19 == | == March 19 == | ||