Open migfoo02 opened 11 months ago
We have already identified this issue caused by duplicate event names and have already put it down in the Planned Enhancements section of the DG. For now, you can mitigate this issue by setting the event name as clean beach 1
, clean beach 2
etc. to distinguish between different sessions as well.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
I changed the date from 30/11/2023 to 23/11/2023 but kept the other inputs the same - which is reasonable as this could be a recurring event that happens weekly. Unfortunately, the app detects it as a duplicate entry.
This effectively prevents users from adding recurring events to the app - this impedes usage by quite a bit given that many volunteering events operate in this manner.