From 482f729a7ad62e234fe51b9a46dbb7817e3f7795 Mon Sep 17 00:00:00 2001
From: Jeff Bruemmer <jeff.bruemmer@gmail.com>
Date: Thu, 24 Aug 2023 11:54:42 -0400
Subject: [PATCH] note on serialization issues (#32360)

---
 docs/installation-and-operation/serialization.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/installation-and-operation/serialization.md b/docs/installation-and-operation/serialization.md
index c137d9ca626..bb418d922ef 100644
--- a/docs/installation-and-operation/serialization.md
+++ b/docs/installation-and-operation/serialization.md
@@ -12,6 +12,8 @@ Once you really get rolling with Metabase, it's often the case that you'll have
 
 To help you out in situations like this, Metabase has a serialization feature which lets you create an _export_ of the contents of a Metabase that can then be _imported_ into one or more Metabases.
 
+> We're interested in how we can improve serialization to suit your workflow. [Upvote an existing issue](https://github.com/metabase/metabase/issues?q=is%3Aissue+is%3Aopen+serialization+label%3AOperation%2FSerialization) to let us know it's important to you. If a relevant issue doesn't yet exist, please create one and tell us what you need.
+
 ## Serialization use cases
 
 - **Staging environments**. Enable a staging-to-production workflow for important dashboards by exporting from a staging instance of Metabase and then importing them into your production instance(s).
-- 
GitLab