You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since events have now been split between 'tasks' and 'events', the event types we can define in the app can only be used in tasks, instead of both which should be the logical functionality IMO. And it's even worse that something called 'event type' cannot be used for 'events' but only for 'tasks'.
This causing event types to be completely unusable as I'm much more using events (which have both a start and end date) instead of tasks (which only have a single date), and all my defined 'event types' were, logically, created to be used for events.
If you don't want a single type list to be used for both kind of items, at the very least, we should define a new item called 'task types' for 'tasks' and move back 'event types' to be used for 'events'
The text was updated successfully, but these errors were encountered:
Since events have now been split between 'tasks' and 'events', the event types we can define in the app can only be used in tasks, instead of both which should be the logical functionality IMO. And it's even worse that something called 'event type' cannot be used for 'events' but only for 'tasks'.
This causing event types to be completely unusable as I'm much more using events (which have both a start and end date) instead of tasks (which only have a single date), and all my defined 'event types' were, logically, created to be used for events.
If you don't want a single type list to be used for both kind of items, at the very least, we should define a new item called 'task types' for 'tasks' and move back 'event types' to be used for 'events'
The text was updated successfully, but these errors were encountered: