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: Changing date manually #525

Open
JuliaFreitagBGSt opened this issue Jan 13, 2025 · 2 comments
Open

Campaign: Changing date manually #525

JuliaFreitagBGSt opened this issue Jan 13, 2025 · 2 comments
Labels
Lead:Pollion For this user story / issue, Pollion has the lead. Type:Enhancement New feature or request
Milestone

Comments

@JuliaFreitagBGSt
Copy link

We would like to be able to change the date of entries (doors, posters and flyers).

For example, posters are put up on Saturday and you want to enter all the locations in the app on Sunday, but you can't change the date yet. Or another example, we would now like to enter all information stands from December and the beginning of January retrospectively, which is also not possible without changing the date.

@JuliaFreitagBGSt JuliaFreitagBGSt added Type:Enhancement New feature or request Lead:Pollion For this user story / issue, Pollion has the lead. BTW: critical Absolutely necessary issues - second order labels Jan 13, 2025
@JuliaFreitagBGSt JuliaFreitagBGSt added this to the Release 1 milestone Jan 13, 2025
@Stift
Copy link
Contributor

Stift commented Jan 13, 2025

The information is currently a technical information and I would keep it as such. I'm not sure whether this kind of micro management is useful for a general public as our recommendation is to have the app with you when you hang the posters. What is the added value or workflow for this?
If we want sth like this I would recommend that we provide an override value in the database. But I would also like to have some constraints as we won't need a historical or future poster entry.

@JuliaFreitagBGSt
Copy link
Author

JuliaFreitagBGSt commented Jan 14, 2025

The information is currently a technical information and I would keep it as such. I'm not sure whether this kind of micro management is useful for a general public as our recommendation is to have the app with you when you hang the posters. What is the added value or workflow for this? If we want sth like this I would recommend that we provide an override value in the database. But I would also like to have some constraints as we won't need a historical or future poster entry.

Alright, got it. I'm going to recommend, that users that use the app as described above, should use the notes field for this kind of information.

I'm going to put this Issue in Backlog and in Release 2, so we could think about this some time later

@JuliaFreitagBGSt JuliaFreitagBGSt removed the BTW: critical Absolutely necessary issues - second order label Jan 14, 2025
@JuliaFreitagBGSt JuliaFreitagBGSt modified the milestones: Release 1, Release 2 Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead:Pollion For this user story / issue, Pollion has the lead. Type:Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants