Upgrade to v0.53.x Causing Issues with Public Dashboards

Bug reports
1

We recently upgraded from v0.48.x to v0.53.7, and since then, we’ve encountered several issues with our public shared dashboards:

  1. Linked filters not working on public dashboards

When accessing dashboards via the public link, our linked filters no longer behave as expected. Each filter dropdown shows all available values rather than being scoped to its parent filter. The linked filter logic seems to be broken—but only for public links. When logged into Metabase, everything works as expected. Public access? No bueno.

  1. Filter input causes chart errors

Most of our dashboards include a “Run Number” filter that allows users to select multiple run numbers for comparison. Since the upgrade, when viewing a public shared dashboard, typing a run number into the filter causes all charts on the dashboard to display: “There was a problem displaying this chart.” However, if you refresh the page, the charts load correctly. This issue only affects public dashboards.

  1. Field type keeps resetting in metadata

This may not be related to the upgrade, but our “Run Number” column in the data model keeps reverting to type “Quantity” in the Table Metadata section of the Metabase Admin panel. We keep changing it back to “Category,” but after a few days, it resets again. Since the column is of type Integer in our underlying Postgres DB, I’m concerned this incorrect type is affecting how filters behave.

These all seem like bugs. The first two issues appear to have been introduced sometime between v0.48 and v0.53.7. We’d really appreciate any help or guidance on how to proceed.

2

Can you share the Admin -> Troubleshooting -> Diagnostic Info. You're running which Java version?

3

Sure thing Tony, here you go:

{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"metabase-info": {
"databases": [
"postgres",
"h2"
],
"run-mode": "prod",
"plan-alias": "",
"version": {
"date": "2025-03-25",
"tag": "v0.53.8",
"hash": "e1eecad"
},
"settings": {
"report-timezone": "UTC"
},
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "16.3"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.7.4"
}
}
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "21.0.6+7-LTS",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "21.0.6",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "21.0.6+7-LTS",
"os.name": "Linux",
"os.version": "6.1.0-13-cloud-amd64",
"user.language": "en",
"user.timezone": "GMT"
}
}

We're currently running the dockerized version v0.53.8 Metabase download from Dockerhub. Looks like Java version is 21.0.6+7-LTS.

Since starting the discussion we've upgraded to v0.53.8 in the hopes that it would rectify issues #1 and #2 above but it did not.

Issue #3 hasn't reproduced all week so that may have been caused last week by us restoring our DB in our attempt to revert to our older version. As we've been on the same DB now all week the field has remained a type category.

4

I actually replicated point 1 on my end as well, for reference:

Can you share more detail on point 2? It's not clear to me how to replicate that

5

I just upgraded to a 54.x version and it appears that fixing issue #1 also fixed issue #2 for our team. Thank you @TonyC for logging that issue and getting it fixed so quickly.

1 Like