Per bug 1824010 comment 1, which is reproduced here: > The different events I think would make sense are: > > 1. migration_wizard.opened - with extra data for how many browsers were available to import from. > 2. migration_wizard.browser_selected - which browser was selected, along with the other browsers that weren't selected. > 3. migration_wizard.profile_selected - we almost certainly don't want to record the name or path of the profile, but perhaps we can record an event if a profile _was_ selected, or if we defaulted to one. > 4. migration_wizard.resources_selected - what resource types were selected (for the new migration wizard, we should also record for variant 2 whether or not the user expanded the resource type selector section) > 5. migration_wizard.safari_permissions_requested - if permissions were requested to access the Safari profile directory > 6. migration_wizard.safari_password_file - if the user chose to import passwords from a CSV file from Safari for the new Migration Wizard (this doesn't exist in the old wizard). > 7. migration_wizard.migration_started - migration began (including browser type, resources types) > 8. migration_wizard.migration_finished - migration completed (including browser type, resources types)
Bug 1824786 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Per bug 1824010 comment 1, which is reproduced here: > The different events I think would make sense are: > > 1. migration_wizard.opened - with extra data for how the browsers that were available to import from. > 2. migration_wizard.browser_selected - which browser was selected, along with the other browsers that weren't selected. > 3. migration_wizard.profile_selected - we almost certainly don't want to record the name or path of the profile, but perhaps we can record an event if a profile _was_ selected, or if we defaulted to one. > 4. migration_wizard.resources_selected - what resource types were selected (for the new migration wizard, we should also record for variant 2 whether or not the user expanded the resource type selector section) > 5. migration_wizard.safari_permissions_requested - if permissions were requested to access the Safari profile directory > 6. migration_wizard.safari_password_file - if the user chose to import passwords from a CSV file from Safari for the new Migration Wizard (this doesn't exist in the old wizard). > 7. migration_wizard.migration_started - migration began (including browser type, resources types) > 8. migration_wizard.migration_finished - migration completed (including browser type, resources types)
Per bug 1824010 comment 1, which is reproduced here: > The different events I think would make sense are: > > 1. migration_wizard.opened - when the migration wizard loads > 2. migration_wizard.no_browsers_found - if the user sees the error message that no browsers were found that can be migrated from. > 2. migration_wizard.browser_selected - includes extra_data for the browser that was selected. > 3. migration_wizard.profile_selected - includes extra_data for the browser that the profile is being migrated from > 4. migration_wizard.resources_selected - what resource types were selected (for the new migration wizard, we should also record for variant 2 whether or not the user expanded the resource type selector section), and the migrator key. > 5. migration_wizard.safari_perms - if permissions were requested to access the Safari profile directory > 6. migration_wizard.safari_password_file - if the user chose to import passwords from a CSV file from Safari for the new Migration Wizard (this doesn't exist in the old wizard). > 7. migration_wizard.migration_started - migration began (including browser type, resources types) > 8. migration_wizard.migration_finished - migration completed (including browser type, resources types)