Skip to content
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

Add global push notifications #2187

Closed
ulliholtgrave opened this issue Mar 30, 2023 · 3 comments · Fixed by #2322
Closed

Add global push notifications #2187

ulliholtgrave opened this issue Mar 30, 2023 · 3 comments · Fixed by #2322
Assignees
Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future. 🌈 ui-ux Issues that requires an UI/UX perspective. 😱 effort: high Big change, which requires >12h
Milestone

Comments

@ulliholtgrave
Copy link
Member

Motivation

Some users are registered for multiple regions and if they want to send a push notification for all regions, they have to click through each municipality and manually enter and send the notification. This should be made easier with a way to send a notification for multiple regions at once.

Proposed Solution

One option would be to specify in a regional push notification form that this notification should also be created for other regions assigned to me.

Alternatives

We could create a separate area at the network level where a notification can be created and then selected to which regions it will be sent.

User Story

As a CMS-User, I would like to have the ability to send a push notification to multiple regions assigned to me so I don't have to click through all of them individually.

@ulliholtgrave ulliholtgrave added 💡 feature New feature or request 😱 effort: high Big change, which requires >12h ❗ prio: medium Should be scheduled in the forseeable future. labels Mar 30, 2023
@ulliholtgrave ulliholtgrave added this to the 23Q2 milestone Mar 30, 2023
@ulliholtgrave ulliholtgrave added the 🌈 ui-ux Issues that requires an UI/UX perspective. label Mar 30, 2023
@hauf-toni
Copy link

Design proposal for this issue can be found here, tbd with @ulliholtgrave

@PeterNerlich PeterNerlich self-assigned this Jun 3, 2023
@PeterNerlich
Copy link
Contributor

In the model I would just modify the PushNotification.region to a many to many relationship for now, but how should this be handled later on in #2186 or follow up issues, when they will have to be editable at some point? E.g. if a user with permissions for only one region wants to edit a scheduled notification for also two other regions? Should he just be denied? Allowed to edit, but it actually splits it into a separate one and removes the region reference from the other one? The former sounds weird and confusing, but the latter might just result in absolute chaos, where it ever to happen.

@david-venhoff
Copy link
Member

david-venhoff commented Jun 9, 2023

Another option might be to not change the push notification model and just create multiple push notifications when creating a push notification for multiple regions. That should avoid this problem.

Edit: Of course this causes problems, when a user with sufficient permissions wants to modify all push notifications again, so there would also be downsides to this approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 feature New feature or request ❗ prio: medium Should be scheduled in the forseeable future. 🌈 ui-ux Issues that requires an UI/UX perspective. 😱 effort: high Big change, which requires >12h
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants