Redmine

The reported bug is still not fixed. I saw the submissions and nobody else reported it.
I just updated to Redmine 2.6.1 and the issue still exists - the News Watch functionality doesn't work.

Plam Sim wrote:

[...] News Watch function doesn't work [...] only News watching has issues [...]

[...] News Watch functionality doesn't work [...]

Come one... Please describe in detail what functionality you are exactly expecting to do what, and what it is that 'does not work' as you expect it to?

Ok, I can explain in more details.

1. login in Redmine with user X
2. navigate to News section
3. click on Watch button in the top right corner
4. logout with user X
5. login with another user Y
6. navigate to News and create a new News

By design Redmine has to send email notification to user X in that case. However User X doesn't receive any email notification for news created by the other user Y (user X is watching the news section). This behavior you can see in Redmine 2.6.0 and Redmine 2.6.1 and that is the problem reported by me.

Again, see Submissions.
Give us your using plugin list and related log.
Do your Redmine 2.5 work expectedly?

I don't have Redmine 2.5 to test it. I can provide info only for 2.6.1 (2.6.0 was upgraded) at the moment.

Toshi MARUYAMA wrote:

Do your Redmine 2.5 work expectedly?

Concerning Submissions rules:

1. My Ruby version is listed
ruby 1.9.3p545

2. My database is updated according the official update documentation

3. Detailed information about my system

• your database manager version > MySQL 5.5.22
• your Ruby version > ruby 1.9.3p545
• your Rails version > Rails 4.1.4
• your Redmine version > 2.6.1
• your using plugins:
  Redmine CRM plugin (Light version) RedmineCRM > 3.4.4
  Redmine Invoices plugin (Light version) RedmineCRM > 3.2.3

Concerning the logs - in the log/production.log there is no messages related to the issue. I am not sure which log have to check about email notifications for watch news.

Toshi MARUYAMA wrote:

Again, see Submissions.
Give us your using plugin list and related log.

Thank you very much! The issue is solved.
You can close this issue.