-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notification Administration - Upgrade UI #79
Notification Administration - Upgrade UI #79
Comments
ready for tech review @rdenarie |
Hello my feedback : it isn't default notification for user and per type because the end user could not change these settings. If the administrator define the choice false for the email notification for the type someone request to join a space, the end user could not change it. BUT it's a real big requirement.... So if you want to change the mandatory to default, i will be very happy ! |
This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
Thanks for highlighting it! We have updated this requirement and we will stick to the current behaviour: the admin enables or disables notifications for user. |
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
…- Meeds-io/MIPs#79 This change updates Badges Portlet to not use Juzu anymore which has been deleted from Notifications Admin, the last portlet using Juzu. In addition, this change will adapt some Unit Tests to new behavior of Notification Settings that ensures that users are enabled before sending notification.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
Thank you. Go Fonc :-) |
…- Meeds-io/MIPs#79 This change updates Badges Portlet to not use Juzu anymore which has been deleted from Notifications Admin, the last portlet using Juzu. In addition, this change will adapt some Unit Tests to new behavior of Notification Settings that ensures that users are enabled before sending notification.
#2791) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
|
Go tech added |
…eeds-io/MIPs#79 (#179) This Test will implement the following Test cases: - When disabling a channel from admin, then it is no more proposed to users - Notification sender email form validation
Thanks. PRs merged to develop. |
#2815) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
…- Meeds-io/MIPs#79 (#1195) This change updates Badges Portlet to not use Juzu anymore which has been deleted from Notifications Admin, the last portlet using Juzu. In addition, this change will adapt some Unit Tests to new behavior of Notification Settings that ensures that users are enabled before sending notification.
…eeds-io/MIPs#79 (#179) This Test will implement the following Test cases: - When disabling a channel from admin, then it is no more proposed to users - Notification sender email form validation
…#38) Before this fix, this mfa configuration was in social module. This commit moves the configuration in the correct mfa module.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 (#5) Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 (#5) Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
…6190 - Meeds-io/MIPs#79 (#661) Juzu dependency is deprecated in meeds. We still need it for chat, rh-management and customer space. We move it in eXo side waiting the refactor of these components.
#2815) This change will move Notification Administration UI from Commons into Social, same as the REST API endpoint. The new portlet is defined using Vue instead of Juzu.
Rationale
Notifications Administration UI is not consistent with other platform UI.
Indeed, the following UI is not accurate with what is expected to see:
In addition to the fact that UX is not the best here:
1. Functional Requirements
The UI will be updated to make sure it is consistent with other UI in the platform.
View of future notifications admin page:
With ability for admin to enable/disable any notification by channel type. When disabled, users won't be able to enable it.
With ability for admin to set the notification sender settings with a proper drawer:
2. Technical Requirements
Upgradability
The old portlet
NotificationsAdminJuzuPortlet
has to be replaced in social by a portlet with nameNotificationAdministration
.Other Non Functional Requirements
The new portlet has to be made using Vue & REST endpoints.
4. Software Architecture
Migration strategy
The definition of UI & REST endpoint has to be moved to social. Knowing that the old portlet will be replaced, the
importMode
of administrators portal has to be of typemerge
oroverwrite
.The text was updated successfully, but these errors were encountered: