Permalinks should resolve to the active dashboard based on the current URL slug

What is the problem or goal the end user is trying to solve or accomplish?

The customer wants to enable seamless dashboard versioning without breaking saved permalinks. The current permalink logic ties the URL to a fixed dashboard ID, which means that once a new dashboard version is created and the slug is transferred, previously generated permalinks still point to the old version, not the updated one. This blocks teams from releasing updated dashboards without requiring users to change their links.

How are they solving it currently?

There is no viable workaround. Even if the slug is manually reassigned to the new dashboard, permalinks generated prior to that reassignment still resolve to the original dashboard ID. As slugs must be unique, customers cannot assign the same slug to both dashboards (old and new) during a transition. This causes broken workflows in environments that require invisible dashboard updates.

What is the recommended solution by the Customer?

Allow permalinks to resolve to the current dashboard associated with the slug value instead of the fixed dashboard ID. Ideally, this could be implemented by:

• Enabling a permalink mode that looks up the dashboard slug at runtime and redirects to the latest associated dashboard.

• Providing an optional “redirect on slug change” setting for dashboards.

• Allowing slugs to act as canonical references that persist across dashboard versions.

This behavior is critical for production environments where silent dashboard upgrades are a must.