How to get feedback on Support Studio issues and Sentry integration?

I understand your frustration about not getting visibility into Support Studio issues. Unfortunately, the Support Studio is an internal tool used by the Sanity team for managing support requests, and there isn't currently a public-facing way to check issue status, priority, or get automated updates on tickets you've submitted there.

This is a common pain point in the community. When you submit something through Support Studio, it's essentially a one-way submission unless the support team responds directly. There's no ticket tracking system exposed to users like you'd find with traditional support platforms.

Better Ways to Get Help

For questions like your Sentry integration issue, you're likely to get better community engagement through:

1. Sanity's Discord community - The most active place for real-time discussions and community help
2. GitHub Discussions - Good for feature requests and technical discussions
3. The official support channels through your account dashboard if you're on a paid plan

Regarding Sentry Integration

For your specific question about crash reporting in Sanity Studio: Yes, Sentry integration is definitely possible! Based on a discussion from the community, here's what worked for others:

For Sanity Studio v2 (the older version), the recommended approach was to:

• Place your Sentry initialization code as the first import in your schema.js file
• Ensure the schema part (part:@sanity/base/schema) comes first in the parts array of your sanity.json file

This catches nearly all errors, particularly those related to plugin loading and custom components.

For Sanity Studio v3+ (current version), since the Studio is built on React, you can integrate Sentry just like any React application:

1. Install Sentry's React SDK: npm install @sentry/react
2. Initialize Sentry in your sanity.config.ts:

import * as Sentry from "@sentry/react";
import { defineConfig } from "sanity";

Sentry.init({
  dsn: "your-sentry-dsn",
  integrations: [new Sentry.BrowserTracing()],
  tracesSampleRate: 1.0,
});

export default defineConfig({
  // your config
});

3. Optionally wrap your Studio with a Sentry ErrorBoundary for better error handling

The key is that Studio v3+ is a React application, so standard React error monitoring patterns work well. You might want to be selective about what you track to avoid noise from expected Studio behaviors.

If you want to share more details about your specific implementation challenges, the Discord community is much more active than the Support Studio for getting peer-to-peer help!