I'm looking for a part-time remote job.

Hire me

I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).

Follow me:

Bug #1613

Guarantee that a notification will come to end user

Added by Andriy Lesyuk over 13 years ago. Updated about 13 years ago.

Target version:
Start date:
02 Feb 2011
Due date:
% Done:



Right now Orangutan notifies users about changes made to issues etc. But... There are several problems here:
  1. If Orangutan crashes it won’t notify about changes made until crash (if he have not yet) – that is Orangutan should save the “pool” of notifications somewhere;
  2. It does not take into account user’s Redmine notification settings (see #1029);
  3. It does not send everything in a pool to a user – it sends only notifications less than 5 days old.

I’m not sure about the last. Are you interested in getting notifications older than 5 days?!..

If this should be done better I guess to inform users about older notifications this way:

Orangutan: ... <Actual notification 1> ...
Orangutan: ... <Actual notification 2> ...
Orangutan: ...
Orangutan: ... <Actual notification <N>> ...
Orangutan: There are 10 older notifications... Whould you like to check them?
User: Yes
Orangutan: ... <Old notification 1> ...
Orangutan: ...


#1 Updated by Andriy Lesyuk about 13 years ago

  • Project changed from Orangutan to Orangutan::Redmine

Also available in: Atom PDF

Terms of use | Privacy policy