Mechanism for broadcasting in-webapp messages to certain pages
Bug #670484 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Launchpad, sadly, frequently has partial service degradation. We might lose lots of builders, or the recipe system goes down, or codehosting is down, or something like that.
When such a thing happens, it would help our users if we could show a message in the web UI itself telling them that there is a problem and that we are working on it. We would not want to show the message on all pages, since, for example, codehosting being down doesn't have much relevance to the bug tracker.
| affects: | launchpad → launchpad-foundations |
| Changed in launchpad-foundations: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad-web: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 10.12 |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 670484] Re: Mechanism for broadcasting in-webapp messages to certain pages | #2 |
Revision history for this message
| Jonathan Lange (jml) wrote | #3 |
| Changed in launchpad-web: | |
| milestone: | 10.12 → none |
To post a comment you must log in.
We could add a message area to the base template control it via a featureflag. We can set the scope of a message to a page id and place the message as the value of of flag.