On call schedule isn't showing On-call shift correctly in on-call calendar.Description Post London Upgrade, when a shift extends to next day and has to rotate between two people, the Calendar doesn't display the on-call resource correctly. Steps To Reproduce Navigate to On-Call Scheduling > Create New ScheduleFill in Mandatory Fields and click NextIn Schedule Definition tab, fill No in 'Would you like to use an existing schedule?' and 'Is the shift for this schedule all day?'Fill in Start and End dates such that End Date is next day.Example : Schedule is defined from 21:00 hours present day to 0400 hours next day.Select 'Daily' for 'How often does 1 shift repeat?'Fill any remaining mandatory fields and click NextFill in the member details and click SubmitCheck the On-Call Calendar for the group.USER A should be displayed present day 2100 hrs - 2359hr and on next day there should be another entry for user A from 0000hrs - 0300hrs .However, USERA is being displayed from 2100 hrs - 2359hr on present day and USERB is being displayed for the rest of the shift on next day feb instead of user A from 0000hrs - 0300 hrs Release or EnvironmentPost LondonCauseIntroduction of a new system property from London. When a shift extends to next day and has to rotate between two people, the Calendar doesn't display the on-call resource correctly. ResolutionThis issue was happening because of a new system property introduced in London - "com.snc.on_call_rotation.factor_daily_rotation_interval_all_day".For rotation to happen , it should have value as false. To fix this issue , follow below steps: Create a new user property - "com.snc.on_call_rotation.factor_daily_rotation_interval_all_day"Set Type - boolean and Value - false.Save the record.Clear cache.test Additional InformationNOTE : This property will not affect rotas/schedules created in past. It will only effect rota's which are created after setting this property to false which implies, rotas created in past will show wrong values post upgrade.To avoid this, we need to do a small update in rotas (like make a change , save the record again) .This property will then consider these rotas as well and will show correct result.