Analytics settings - transition the page to WooCommerce settings

[pmcpinto]

Description: the Analytics settings are available under Analytics, which can lead to discoverability issues and a bad user experience, as most settings should be available in WooCommerce - Settings. Also, the legacy reports and orders menu don't respect the Excluded and Actionable statuses which can cause a mismatch in the data displayed across different surface areas

Acceptance criteria:

• Migrate the Analytics - Settings page to a new tab called "Analytics" in Settings. The tab can be displayed after the Payments tab.
• The legacy reports should respect the Excluded and Actionable statuses settings
• We should inform the users who visit Analytics - Settings page about this change. One option is to display a message informing users the page was migrated

Event tracking:
We should keep the Tracks events that already exist in Analytics - Settings
The new Analytics tab in Settings should use wcadmin_settings_change and wcadmin_settings_view

[pmcpinto]

@louwie17 is it possible to get an estimate on the effort to implement these changes? I suspect it will take some work, so I wonder whether we should think about an interim solution.

cc @jarekmorawski in case you have some suggestions.

[louwie17]

@louwie17 is it possible to get an estimate on the effort to implement these changes? I suspect it will take some work, so I wonder whether we should think about an interim solution.

@pmcpinto here are the estimates, I have it split up a bit, as there are some items that are harder to do:

Migrate the Analytics - Settings page to a new tab called "Analytics" in Settings. The tab can be displayed after the Payments tab.

• Moving the excluded/actionable status and date type fields - Max 2 days (should be relatively straight forward, as these field types are supported by the Settings API )
• Moving the default date range field - 2 days in itself ( as I don't think this field is supported by the settings API, so we did have to add support for that )
• Import Historical data - 3 days ( requires a separate UI within the settings menu, do we want to move this to a separate tab within the Analytics settings page? )

The legacy reports should respect the Excluded and Actionable statuses settings

~1 day (should be relatively straight forward )

We should inform the users who visit Analytics - Settings page about this change. One option is to display a message informing users the page was migrated

~1 day ( should be pretty easy )

We did probably want to split all these tasks up into separate issues as listed/pointed above.

[pmcpinto]

Lourens, thanks for the quick feedback. We could break it into 2 iterations to decrease the scope:

i1:
Moving the excluded/actionable status and date type fields
Moving the default date range field
The legacy reports should respect the Excluded and Actionable statuses settings
Inform the users who visit Analytics - Settings page about this change
Rename Analytics - Settings to Analytics - Import data

i2
Moving the import historical data (we should evaluate if it makes sense to move the feature as this isn't a setting)

What do you think?