[BUG] Not all default routes are translated correctly when upgrading to Dashboards

[tmarkley]

Describe the bug

When upgrading from ODFE 1.x or Kibana 7.x to Dashboards 1.0, not all default routes are migrated to the new routes if names have changed.

To Reproduce
Steps to reproduce the behavior:

1. Follow the BWC testing instructions but use a default route such as /app/opendistro-alerting or /app/kibana#/dashboard/722b74f0-b882-11e8-a6d9-e546fe2bba5f
2. Upgrade to Dashboards 1.0
3. Notice the 404 when loading for the first time. There is no option provided to the customer to fix this.
4. The user must manually edit the URL to access Dashboards.

Expected behavior
Some initial ideas:

• Generic translation that takes anything with opendistro or kibana and replaces with the dashboards equivalent
• Have a list of equivalent routes for all known routes in ODFE or Kibana that changed in Dashboards and execute a replace for the user's default route.
• Have an automated check for a default route that 404's and revert back to the default.
  • OR if the default route 404's, let the user choose the correct default route before continuing so that it can be fixed.

OpenSearch Version
1.0.0

Dashboards Version
1.0.0

Plugins

N/A

[kavilla]

• Generic translation that takes anything with opendistro or kibana and replaces with the dashboards equivalent
• Have a list of equivalent routes for all known routes in ODFE or Kibana that changed in Dashboards and execute a replace for the user's default route.

For the original, I was too worried about generically replacing kibana/opendistro.

The third option we could revert it back to default or I was thinking have a button that lets them go back to app home and potentially another button to take them to settings?

What do you think @tmarkley ? @ahopp as well.

[tmarkley]

I like giving the user options. Would we want to edit the 404 experience in general so that in all cases they have the ability to go back to app home or settings?

I'd be hesitant to revert it back to default without asking the user first.

[kavilla]

I'd be hesitant to revert it back to default without asking the user first.

Same.

It could be easy to provide a button to app home but it might be difficult to determine if the user got to the 404 page because their default route took them there or some other way.

[kavilla]

Looked into this and was not a trivial solution. Likely not achievable for 2.0.0