Burndown charts local timezone alters milestone start date

The following discussion from !15463 (merged) should be addressed:

  • @mikegreiling started a discussion: (+1 comment)

    This all works correctly, but I did notice one odd thing. Although I set configured the start and end date correctly, the actual data appears to start one day earlier, with a count/weight of 0. This throws off the guideline rendering and looks pretty ugly. I'm fairly certain this has to do with recent adjustments made to support local timezones.

    before: Screen_Shot_2019-10-10_at_6.09.25_PM

    after: Screen_Shot_2019-10-10_at_6.09.14_PM