Broadcasts - Add start and expiration date fields

Please consider creating a start & expiration date field for broadcasts.  This would be useful so that the admin can 'schedule' the messages and store future messages for delivery.  If implemented, please include timezone so the admin knows exactly when the message will be activated/deactivated.  Thanks!

  • Joe Carpenter
  • Dec 11 2015
  • Likely to implement
Release time frame
  • Attach files
  • Joe Carpenter commented
    September 13, 2017 15:42

    Checking on the status of this - is it possible to have this implemented soon? 

    With all the AWESOME* changes that the Aha team is making, I want to keep the user base apprised of the new features and the most effective way to do that is via Broadcasts. Many users are becoming numb to them though as the same broadcast sits there for a very long time, hence the need for a scheduling feature for the #broadcasts.

     

    * - Shameless fawning in an effort to get this built sooner than later!

  • Admin
    Chris Waters commented
    September 13, 2017 17:02

    Broadcasts are designed for the user to close them after they are read. However, we see the same problem that you do where users don't close the broadcast and just leave it open. I would love to have a better solution to that problem, rather than scheduling of the broadcasts.

  • Joe Carpenter commented
    September 13, 2017 17:08

    Makes sense, this idea (and my related one) are intended to try to solve that.

    Some broadcasts are only relevant for a period of time (Solved by expiration dates)

    Some broadcasts only need to be displayed X times (solved by a view count)

    Regardless of the strategy taken above, the ability to schedule a broadcast is a common need (i.e. if the Admin is going to be on vacation but wants to activate a Broadcast in the future..)