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

Campaign: Member coordination in the app #549

Open
JuliaFreitagBGSt opened this issue Jan 21, 2025 · 1 comment
Open

Campaign: Member coordination in the app #549

JuliaFreitagBGSt opened this issue Jan 21, 2025 · 1 comment
Labels
BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:Enhancement New feature or request
Milestone

Comments

@JuliaFreitagBGSt
Copy link

Is your feature request related to a problem? Please describe.
Members are currently sharing lists in the Grüne Wolke to coordinate the campaign and the members, but these wolke-lists only work very poorly via browser, especially on cell phones.

Describe the solution you'd like
It would be desirable to be able to plan staff for the election campaign in the app. The following functions would be necessary: assignment of rights, who can set appointments and for which election campaign form; filter function according to OV and KV.
Also Appointments: Which election campaign form, meeting point, date, time (start and optionally end time); it would also be ideal if you could set the minimum number of experienced people needed (especially for HTWK and WKS) as well as text/instructions (e.g. which streets will be made or whether something else needs to be brought along, etc.). Then the people can use the app to enter their experience for each type of campaign and book themselves for appointments.

Describe alternatives you've considered
Alternatively, this could be developed in the atlas and would only be displayed in the app and only appointments could be confirmed in the app.

Additional context
This is something for later (Release 3), when the Atlas is further developed.

@JuliaFreitagBGSt JuliaFreitagBGSt added BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:Enhancement New feature or request labels Jan 21, 2025
@JuliaFreitagBGSt JuliaFreitagBGSt added this to the Release 3 milestone Jan 21, 2025
@JuliaFreitagBGSt
Copy link
Author

JuliaFreitagBGSt commented Jan 21, 2025

Created an Issue in gruenes-netz-admin (#61) and gruene-api (#138) as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BTW: non-critical Less important issues (for after BTW) Lead:Pollion For this user story / issue, Pollion has the lead. question The technical and/or design implementation requires further specification Type:Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant