getsentry / getsentry/sentry

Email notification is sent right after issue marked as completed

Open
#124,170 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Product Area: Settings Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce
  1. Complete an issue
Expected Result

No email notification should be send on issue completion

Actual Result

Email notification is sent. Even inside this email the issue has already completed status and it's title is crossedout.

Product Area

Issues

Link

No response

DSN

No response

Version

No response

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

No file, test, or entry point is named. Start by reproducing the issue from the listed steps in the Issues area and trace the completion notification flow. Done means completing an issue does not send an email notification, including when the email would show the issue as completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.