[ADMINCTR-285] Display a global banner ahead of planned downtime Created: 05/Oct/22  Updated: 16/Feb/23

Status: Open
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-8019 Add a new scope for logged in users t... Open
causality
relation
supersession
supersedes MGNLSSO-90 SSO-Users not receiving Messages when... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: SSO maintenance
Team: AdminX

 Description   

Quoting from cchard at MGNLSSO-90:

Our use case is quite simple: We would like to let all currently active editors know that we will be performing a release (short downtime in authoring). "Please save your work and grab a cup of coffee. Magnolia will be restarted in 5 Minutes and back very soon."

We do this currently by sending emails, but it would be "nice" to be able to relay an additional message to active users in system.

Mainly we shouldn't be using the messages app to send such announcements, because messages are not compatible with external users (see comment).



 Comments   
Comment by Roman Kovařík [ 05/Oct/22 ]

The admincentral component was extracted into https://jira.magnolia-cms.com/projects/ADMINCTR, should we move the ticket?

Edit: there seems to be a fix for the original problem described in a comment below so the ticket might stay in UI project.

miruela Should we score this/ relink the support ticket or is the support ticket closed?

Comment by Roman Kovařík [ 05/Oct/22 ]

I've checked the problem and as pointed out, we can't get all users for external system here https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/browse/magnolia-ui-framework-jcr/src/main/java/info/magnolia/ui/framework/message/MessagesManagerImpl.java#85, but we can fallback to all logged in users like this ~:

users = listeners.keySet().stream()
                    .map(userManager::getUser)
                    .collect(Collectors.toSet());

as we have a map of listeners per all logged in user.

Comment by Mikaël Geljić [ 06/Oct/22 ]

Sounds like a good addition on the one hand—thank you all for the suggestion and pointer!—On the other hand, users logging in after the message is sent will not see anything, right? I'll move that story to ADMINCTR anyhow (old habits), then we see how/where we can address it best.

Generated at Sun Feb 11 23:05:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.