-
Notifications
You must be signed in to change notification settings - Fork 2
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
Default selected audit year not just datetime.now().year
#460
Comments
We also need the audit selector to work for 23-24 as the plan is to validate the KPI calculations by re-uploading all the CSV files from the last audit year into the new platform. Should I expand the scope of this issue to cover that or raise a separate one? |
That should be an easy fix, if we only use this Can just increase lower bound to work for 23-24, can't remember if it already does |
Reopening as there's some other instances of |
Yep this is what i wanted to confirm with @eatyourpeas whether adjusting the default setting would affect other things |
They all need updating - at the moment on live if you upload a CSV you can’t see it because the CSV code is using date.today().year but the switcher is correctly using audit year. PR incoming |
@eatyourpeas was looking to update this myself now but unsure if it's set / used in multiple places, and unsure if I'm right, so wanted to confirm with you
Currently
session.py::65
, in return ofcreate_session_object()
, we set the defaultselected_audit_year
as:But I think that because audit periods are laid out like:
the default audit year for e.g.
4 Jan 2025
ISNT2025
but is2024
?We have a
get_audit_period_for_date()
fn insidegeneral_functions/audit_period.py
that gets audit period for given date so simplest change could be like:The text was updated successfully, but these errors were encountered: