[Bug] [Notification] mentiont user on not-watching-repo = no notification #4435

@6543 commented on GitHub (Dec 3, 2019):

@guillep2k sory for the les sinfos ... working on the empty issue dashboard!

@6543 commented on GitHub (Dec 3, 2019): @guillep2k sory for the les sinfos ... working on the empty issue dashboard!

GiteaMirror commented

@6543 commented on GitHub (Dec 27, 2019):

this bug is stil anoying and block work on gitea.com :(

@6543 commented on GitHub (Dec 27, 2019): this bug is stil anoying and block work on gitea.com :(

GiteaMirror commented

@guillep2k commented on GitHub (Jan 7, 2020):

Sorry, @6543, I can't reproduce. With current master (b6fa229dcf), I did the following:

I've created a public repo with user1 (user1/publicrepo).
With user1, I've created an issue in that repo with the following description: I mention @user2.
user2, who wasn't watching that repo, got a proper mail notification.
With user2, I set to watch user1/publicrepo. Then I set it to unwatch user1/publicrepo in order to created an explicit unwatch.
With user1, I've created a new issue with the following description: I mention @user2 again.
user2, who explicitly unwatched that repo, got a proper mail notification.

I didn't get anything in user2's dashboard, however. Is that what your issue is about?

@guillep2k commented on GitHub (Jan 7, 2020): Sorry, @6543, I can't reproduce. With current `master` (b6fa229dcfbe4ad64fe758ef92abaf7a80e6f700), I did the following: * I've created a public repo with **user1** (`user1/publicrepo`). * With **user1**, I've created an issue in that repo with the following description: `I mention @user2`. * **user2**, who wasn't watching that repo, got a proper mail notification. * With **user2**, I set to watch `user1/publicrepo`. Then I set it to _unwatch_ `user1/publicrepo` in order to created an explicit unwatch. * With **user1**, I've created a new issue with the following description: `I mention @user2 again`. * **user2**, who explicitly unwatched that repo, got a proper mail notification. I didn't get anything in **user2**'s _dashboard_, however. Is that what your issue is about?

GiteaMirror commented

@6543 commented on GitHub (Jan 7, 2020):

I'll look & test later :)

@6543 commented on GitHub (Jan 7, 2020): I'll look & test later :)

GiteaMirror commented

@6543 commented on GitHub (Feb 12, 2020):

tested with newest version:

user1 create repo (or has one witch user2 not watching)
user1 create issue
user1 create comment "soething @user2"
user2 get NO notify

also tested:

user1 create repo (or has one witch user2 not watching)
user1 create issue witch mention user2
user2 get NO notify

PS: I didn't checked the mail notify but web-UI show no new notification

@6543 commented on GitHub (Feb 12, 2020): tested with newest version: 1. user1 create repo (or has one witch user2 not watching) 2. user1 create issue 3. user1 create comment "soething @user2" 4. user2 get NO notify also tested: 1. user1 create repo (or has one witch user2 not watching) 2. user1 create issue witch mention **user2** 4. user2 get NO notify PS: I didn't checked the mail notify but web-UI show no new notification

GiteaMirror commented

@6543 commented on GitHub (Feb 19, 2020):

@guillep2k just noticed yor question - yes its about gezing notify on UI too

@6543 commented on GitHub (Feb 19, 2020): @guillep2k just noticed yor question - yes its about gezing notify on UI too

GiteaMirror commented

@6543 commented on GitHub (Mar 3, 2020):

~~one of the next things I'll work on~~
I wokred on that ... but it had a other result ;)

@6543 commented on GitHub (Mar 3, 2020): ~~one of the next things I'll work on~~ I wokred on that ... but it had a other result ;)

GiteaMirror commented

@stale[bot] commented on GitHub (May 2, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 2, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

@6543 commented on GitHub (May 2, 2020):

I'll test it this still is the case ...

@6543 commented on GitHub (May 2, 2020): I'll test it this still is the case ...

GiteaMirror commented

@stale[bot] commented on GitHub (Jul 3, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 3, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

@6543 commented on GitHub (Jul 4, 2020):

Its in current master still the case

@6543 commented on GitHub (Jul 4, 2020): Its in current master still the case

GiteaMirror commented

@stale[bot] commented on GitHub (Sep 2, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Sep 2, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented