Feature #332
Provide a notification mechanism
| Status: | Closed | Start: | 06/25/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Paul Kelly |
% Done: | 0% |
|
| Category: | Web Interface | |||
| Target version: | 0.1-6 | |||
| Backlog: | Difficulity: | |||
| Votes: | 0 |
Description
When an upgrade is performed there should be a mechanism for informing the user(s) about manual actions that should be performed.
An API should be provided to cause a message to be displayed on all screens that a user visits, together with a button to remove the message. The message should be either "global" or "individual". If global, then the first user to click the "acknowledge" will close the message for all users. If the message is not "global" then each user of the system will have to signal acknowledgment of the notice.
Related issues
| blocked by Foreman - Refactor #390: Ensure that a user account is always selected | Closed | 09/29/2010 |
History
Updated by Paul Kelly over 1 year ago
- Status changed from New to Ready For Testing
- Branch set to feature/332-notifications
Added a level argument that changes the message icon.
It is now more visually appealing.
Updated by Paul Kelly over 1 year ago
Fixed issue where the admin user lookup was not being cached in the session when SETTINGS[:login] was not true
rebased
tested
Updated by Ohad Levy over 1 year ago
- Target version set to 0.1-6
Updated by Ohad Levy over 1 year ago
- File 0001-my-mods-suggestions.patch added
my mods, please review and update if needed
Updated by Ohad Levy over 1 year ago
- File deleted (
0001-my-mods-suggestions.patch)
Updated by Ohad Levy over 1 year ago
- File 0001-my-mods-suggestions.patch added
new version of the patch
Updated by Paul Kelly over 1 year ago
Fixed some broken tests and some bogus references to User.current
Also test_helper#set_session_user was wrong. Ouch.
rebased and tested
Updated by Ohad Levy over 1 year ago
- Status changed from Ready For Testing to Closed
