Change Details

//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4119 // == Context == ULS analytics schemas must be optimized after a first iteration of analysis. This was recommended by several WMF analytics experts as a good practice. == Narrative == As a product manager in WMF, I can get relevant data about usage, so that I can improve the products. == //Acceptance Criteria// == * Remove events that are not useful for analysis. * Add events that may be useful. * Split a big schema with recycled fields (as UniversalLanguageSelector_7327441 is now) to several small focused schemas. * For all of these - update the schema and the ULS code that writes to the schema. == //Deliverables// == * //Enter link to actually done tangible deliverable(s)// == //Open tasks// == {{ table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' < 'Done' ORDER BY 'Task Status', Owner, Name }} == //Completed tasks// == {{ table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Actual effort(hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' = 'Done' ORDER BY 'Task Status', Owner, Name }} == ==

//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4119 // == Context == ULS analytics schemas must be optimized after a first iteration of analysis. This was recommended by several WMF analytics experts as a good practice. == Narrative == As a product manager in WMF, I can get relevant data about usage, so that I can improve the products. == //Acceptance Criteria// == * Remove events that are not useful for analysis. * Add events that may be useful. * Split a big schema with recycled fields (as UniversalLanguageSelector_7327441 is now) to several small focused schemas. * For all of these - update the schema and the ULS code that writes to the schema.

//Migrated from: https://wikimedia.mingle.thoughtworks.com/projects/language_engineering/cards/4119 // == Context == ULS analytics schemas must be optimized after a first iteration of analysis. This was recommended by several WMF analytics experts as a good practice. == Narrative == As a product manager in WMF, I can get relevant data about usage, so that I can improve the products. == //Acceptance Criteria// == * Remove events that are not useful for analysis. * Add events that may be useful. * Split a big schema with recycled fields (as UniversalLanguageSelector_7327441 is now) to several small focused schemas. * For all of these - update the schema and the ULS code that writes to the schema. == //Deliverables// == * //Enter link to actually done tangible deliverable(s)// == //Open tasks// == {{ table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' < 'Done' ORDER BY 'Task Status', Owner, Name }} == //Completed tasks// == {{ table query: SELECT Number, Name, Owner, 'Estimated effort (hrs)', 'Actual effort(hrs)', 'Task Status' WHERE Type = Task and 'Schedule - Story' = THIS CARD and 'Task Status' = 'Done' ORDER BY 'Task Status', Owner, Name }} == ==