metabase / metabase/metabase

Configure recipients for transform notifications

Open
#74,777 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

.Auto triaged .Team/Gadget Transforms Type:New Feature
Dominant language
Clojure
Stars
49.3k
Forks
6.8k
Avg merge
1d 13h
Merged PRs (30d)
653

Description

**What problem will this feature request solve?**
Currently, notifications on failed transforms are sent to all instance admins.

- Imagine I work at a 3000 people company on a team of 50 analysts. There are product analysts, and marketing analysts, and people analysts etc and they all got their own thing going on. If I'm doing product analytics, why do I care that someone's marketing transform failed? I won't even have the knowledge to fix it, I'll just keep getting spam emails that are irrelevant to me.

- Imagine I'm a metabase admin because I'm the org's infrastructure/security person. I don't know how to fix any failing transforms - I'm not a data guy! These notifications are just non-actionable noise to me.

**Describe the solution you'd like.**
Configure who gets notifications about transforms. Give people the ability to unsubscribe from specific transform notifications

**How does this feature request impact you?**
Real annoying

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how failed transform notifications currently determine their recipients. Define the configuration and unsubscribe behavior needed for transform-specific notifications, then verify that admins no longer receive irrelevant alerts while intended recipients still do. The issue names no files or tests, so the relevant entry points must be located in the repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.