Classic dashboard upgrade : #dashboard links should be upgraded to #classic-dashboard

[del65]

This is an issue with the upgrade process : links are kept in Markdown tiles.

But I discovered you can still access the not upgraded classic dashboards form their old ID by replacing #dashboard with #classic-dashboard.

This replacement should have been done automatically in the upgrade process.

Subsidiary questions:

If I use the #classic-dashboard to link to an upgraded dashboard with tts old "classic" ID, I am redirected to the upgraded one automatically.

1. how can I prevent this feature if the upgraded dashboard is not ready yet ?

2. is there some sort of "draft" mode to avoid pushing dashboard upgrades to users until ready ?
I found dashboards to be quite difficult to improve without (temporary) regressions when any change is saved, published and added to the history.

3. if the upgraded dashboard is made "draft" or "private" by me as owner (while being worked on to match classic dashboard features...) can other users still view the classic dashboard instead of an "access right" failure ?

[MaximilianoML]

Hello @del65!

I think you have found two separate topics here:

1. Markdown links not being rewritten during the upgrade
2. The mapping behavior between the old Classic dashboard ID and the upgraded Dashboard

For the first point, I agree with you. This feels like something the upgrade process should handle automatically, or at least something that should be clearly mentioned as a manual post-upgrade task. Since Markdown tiles can include links to other dashboards, having those links still pointing to old or unexpected locations after the upgrade can easily become a migration issue.

For the second point, from what you described, it looks like Dynatrace keeps a relationship between the old Classic dashboard ID and the upgraded dashboard. That would explain why opening the old Classic dashboard link redirects users to the upgraded version. As far as I know, I don’t think there is currently an option to disable that redirect for a specific dashboard.

For your questions:

1. How can I prevent the redirect if the upgraded dashboard is not ready yet?

The safest workaround is not to upgrade the production/shared Classic dashboard directly. Instead, clone the Classic dashboard first, then upgrade the clone and work on that upgraded copy. Classic dashboards support cloning, and the original dashboard remains unaffected when a clone is created.

2. Is there a draft mode to avoid pushing upgrades to users until ready?

As far as I know, there is no true “draft/publish” lifecycle for upgraded dashboards where changes are hidden until explicitly published. New Dashboards are document-like objects with sharing/access controls, but saved changes are reflected in the dashboard itself. Dynatrace documents that dashboards/notebooks can be shared with everyone, specific users/groups, or via links, but that is access control rather than a release workflow. So the practical workaround is again to work on a private cloned/upgraded copy, validate it, and only share or replace links once it is ready.

3. If I make the upgraded dashboard private, can other users still view the Classic dashboard instead?

I would not rely on that. If the old Classic ID is already mapped/redirected to the upgraded dashboard, making the upgraded dashboard private may result in users being redirected to a dashboard they cannot access, instead of falling back to the Classic one. So I would avoid upgrading the original shared Classic dashboard until the new version is production-ready. Use a clone for migration/testing, then update links or communicate the new dashboard when ready.

I hope it helps you 😁