When I edit a project which existed before (in the view of the Budgeteer data model) a project had a start and end date, in its administration view the project time frame is displayed as the current year, e.g. 1/1/19–12/31/19. This works as expected, as it was the required migrational view.

Now that I come and enter the real date data of the project, e.g., 1/1/16–12/31/16 and save, the view confirms the successful storage of the time frame and... reverts the view to 1/1/19–12/31/19.

It should not be necessary to reload the view to see the correctly stored (but incorrectly not displayed) new project time frame.

As it is a migrational issue, the priority is pretty low. Then again, it should be easy to fix and a good educational example.