| title |
|---|
How to find a known bug or limitation |
If you can't find or solve your problem using the troubleshooting guides, you may be running into an issue that we're still working on.
If your work in Metabase is crashing, missing, or not being saved, you might have found a bug.
-
Go to the Metabase Github issues page.
-
Click on the Label dropdown and select
Type: Bug.If you're encountering problems after your Metabase version was recently upgraded, you can add the label
.Regression. -
Choose least one value in the Label dropdown that matches the feature you're having trouble with.
Add additional keywords to the search bar above the list of results. Hit Enter/Return to run the search.
Click Sort and select the thumbs up emoji (👍) to view the most commonly encountered bugs.
-
If you find an existing bug that matches your problem, add a thumbs up emoji to help the team prioritize it.
-
If you can't find your problem, and you're sure that it's not a product limitation, you can create a new bug report.
If the functionality you're looking for simply doesn't exist (i.e., it hasn't suddenly gone missing), you might be running into a product limitation.
-
Go to the Metabase Github issues page.
-
Click on the Label dropdown and select
Type: New Feature. -
Choose least one value in the Label dropdown that matches the feature you're looking for.
Add additional keywords to the search bar above the list of results. Hit Enter/Return to run the search.
Click Sort and select the thumbs up emoji (👍) to view the most highly requested features.
-
If you find a feature request that matches what you want to do, add a thumbs up emoji to help the team prioritize it.
-
If a feature request doesn't exist, and your issue isn't caused by a known bug, you can submit a new feature request.