Changes between Version 1 and Version 2 of Ticket #1055


Ignore:
Timestamp:
Sep 9, 2008, 3:08:32 PM (16 years ago)
Author:
Jari Häkkinen
Comment:

This ticket was split to this ticket, ticket:1113, and ticket:1114.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1055

    • Property Milestone → BASE 2.x+

  • Ticket #1055 – Description

    v1 v2  
    1 I think we should create a messaging system for BASE. There are situations where you want to send a notification to users. Planned system down time, or more urgent system is going to be rebooted very soon. One could even imaging announcements about new features, plug-ins, and extensions.
    2 
    31The messaging system should allow users with proper credential to send messages to users in a BASE installation. This can be either through the messaging system built into BASE or sending emails to users through BASE.
    42
    53Users should be able set messaging preferences like 'accept no message', 'accept messages from this set (of groups, projects, users)', 'do not accept messages from ...'. Messages from administrators should never be disallowed.
    6 
    7 For urgent messages like restart of BASE it would be nice to be able to send a broadcast to currently logged in users. The problem is to push the messages, but maybe one could display a message at the next interaction of logged in users? While doing this kind of interruptions maybe we should support blocking of login to BASE. I am thinking of a situation where one would like to restart BASE. The first step would be to disallow logins and then sending a message to active users, asking them to logout/save within a certain time, then restart BASE or do whatever is needed. The block login feature request should probably have its own ticket.