97183 - System message architecture.

Status: NEW

(Bugzilla :: Bugzilla-General, enhancement, P3)

Description

[Matthew Tuck [:CodeMachine]]

We need a way of popping system messages up to a user in the footer or page
header or whatever.  Uses include:

- messages to a person or group from an administrator
- "Bugzilla will be down" messages to everyone from an administrator
- messages popped up by Bugzilla to specific people in specific circumstances
(eg "fix your votes" (bug #95609) or "there is a new feature" (eg the current
message on bug mail about the email preferences)).

Administrator messages could have their start and end times defined as well as
who they are for, and Bugzilla messages would be schedules appropriately by
Bugzilla.

Comment 1

[Matthew Tuck [:CodeMachine]]

These messages should probably also appear on emails that get sent out.

Comment 2

[Jouni Heikniemi]

Maybe the email inclusion should be optional per message. Some notifications
don't necessarily deserve email space. 

Comment 3

[Gervase Markham [:gerv]]

What situations does blurbhtml not cover? Is there actually administrator demand
for the specifically-targetted and/or timed stuff?

Gerv

Comment 4

[Dave Miller [:justdave]]

Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them. (sorry for
the spam if you got this twice, it didn't take right the first time)

Comment 5

[Frédéric Buclin]

It's high time to revive this bug. Let's get it in 2.24.

Comment 6

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 7

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.