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

[USABILITY] Displaying recurring events #4737

Open
vburgett opened this issue Feb 5, 2025 · 1 comment
Open

[USABILITY] Displaying recurring events #4737

vburgett opened this issue Feb 5, 2025 · 1 comment
Assignees
Labels
Priority: High High priority

Comments

@vburgett
Copy link

vburgett commented Feb 5, 2025

The Illinois app displays recurring events that come from the app, Fusion, and Webtools. Ideally all these recurring events display the same way.

For the recurring events made on the website/app, please display the event with one of the below options:

  1. Replace the date range with a specific event day. See screenshot below. Display the recurring event in the feed multiple times based on each particular day in the recurrence. (This is how recurring Webtools events work. See the Meditation screenshot in this ticket.)

OR

  1. Display each event of a recurring event separately with no repeating dates displayed. An event admin should still only have to edit one recurring event entry to change all events in the recurrence. (This is how recurring Fusion events display. See "Zumba" in the app.)

cc: @dobromirdobrev

Image

@mihail-varbanov
Copy link
Collaborator

@pmarkhennessy, I am not 100% what @vburgett exactly wants in this issue, but my belief is that what she wants is to change the way we supply the recurrent events in the events feed. It would be safer and more efficient if @dobromirdobrev took on this as historically he was doing this stuff in Events and he just made changes there quite recently. I see things there that I don't quite understand, and I'm not sure if I'm going to break something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High High priority
Projects
None yet
Development

No branches or pull requests

4 participants