IO-740 & IO-789 Classify dotted POSIDs by last segment#431
Open
cyanidesayonara wants to merge 2 commits intodevelopfrom
Open
IO-740 & IO-789 Classify dotted POSIDs by last segment#431cyanidesayonara wants to merge 2 commits intodevelopfrom
cyanidesayonara wants to merge 2 commits intodevelopfrom
Conversation
* Dotted POSIDs (e.g. 2814I04749.03.01) now classify by the LAST non-empty segment instead of the first, so Karhusuontie's .03.01 bookings land in planning (leaf task 01) while .03.02 / .03.01.03 / .03.01.05 stay in construction * Add --force-refetch flag to fetchsapdatabyyear so frozen 2025 rows can be rewritten once after deploy (IO-790 freeze otherwise returns the stale DB row)
* Restore subproject "000" fallback in concat branch * Add regression tests for Karhusuontie (2814I04749), Valtimontie (2814I00720) and Karamzininranta (2814I03976) using the actual amounts from prod sync logs * Add unit tests for --force-refetch
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploy / post-merge steps
sapsynchronizerwill correctly re-classify 2026 data on the next run with no manual step.oc exec -- python manage.py fetchsapdatabyyear --year 2025 --force-refetch
Only needs to be run once, after deploy.
UAT checklist
After step 3 above, verify on the projects named in the tickets:
.03.01bookings should now appear under planning (Suunnittelu), not construction.