Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding beginning and end to a late project #383

Open
tinne opened this issue Nov 13, 2019 · 0 comments · May be fixed by #438
Open

Adding beginning and end to a late project #383

tinne opened this issue Nov 13, 2019 · 0 comments · May be fixed by #438

Comments

@tinne
Copy link
Member

tinne commented Nov 13, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants