Closed yyy2356 closed 1 month ago
only you have had your total hours cutoff by this, so we need to fix your time. the total seconds has it backed up, luckily.
I think that maybe only the model needed to be changed, luckily. Everything seems to be working after doing the migration on development.
1 i made a branch for you 2 why don't we just get rid of that all together? We are storing the same value twice. I say just use the total seconds
There was probably some reason... maybe it was just copied over from the original and they needed it for some reason that isn't relevant anymore. Storing it twice might be a good idea anyways for redundancy, and all the infrastructure for it is set up. The change was pretty simple.
my current pr should fix it, less changes needed to be made than i thought as django is pretty resilient.
i overestimated the difficulty, all that needs to happen is fixing your total hours and implementing the changes made in the pr before todays meeting.
Change total_hours to a duration field and change all the views and anything that references it to accommodate that.