Open jaragunde opened 6 years ago
Maybe we should simplify this feature and allow only one default journey value per year assigned to a city/work calendar. It would fit well with the implementation of #359, and it's likely that we don't need such a fine-grain configuration to this, we still have user journeys for that.
Following the previous example, results would be exactly the same with a configuration for City like this: 2018 -> 8 hours, no configuration for 2019.
When a organization-wide change to work journey happens, it's painful to apply it to every active user in the system.
The idea is to allow cities/work calendars to contain this information about work journeys: start, end dates and daily journey. Users will be applied this configuration as long as they are assigned to that city/work calendar, and in case they don't have their own journey values overwriting it.
Example: