github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Assigning an issue does not send an email if user's notifications are set to "Only on Mention" #8208

New Issue
Closed
opened 2025-11-02 07:57:37 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:57:37 -06:00
Owner
Copy Link

Originally created by @greatawesome on GitHub (Dec 2, 2021).

Feature Description

It would be ideal if assigning a user an issue (as per #8233 and #8546) would be considered a "mention" for the purposes of sending email notifications.

Screenshots

No response

Originally created by @greatawesome on GitHub (Dec 2, 2021). ### Feature Description It would be ideal if assigning a user an issue (as per #8233 and #8546) would be considered a "mention" for the purposes of sending email notifications. ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 07:57:37 -06:00
GiteaMirror commented 2025-11-02 07:57:39 -06:00
Author
Owner
Copy Link

@flozzone commented on GitHub (Feb 10, 2022):

came across this too now. would be very helpful and users expect a notification email when they got assigned also if they've On mention setting enabled.

@flozzone commented on GitHub (Feb 10, 2022): came across this too now. would be very helpful and users expect a notification email when they got assigned also if they've `On mention` setting enabled.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8208
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?