-
Notifications
You must be signed in to change notification settings - Fork 35
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
B 21904 nts oconus int #14384
base: integrationTesting
Are you sure you want to change the base?
B 21904 nts oconus int #14384
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just 1 minor thing to check - everything else looks good to me.
migrations/app/schema/20241208080706_add_internatinoal_nts_re_service_items.up.sql
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
testing: success
code: lgtm
INSERT INTO re_service_items | ||
(id, service_id, shipment_type, market_code, is_auto_approved, created_at, updated_at, sort) | ||
VALUES | ||
('2a560507-db09-4be1-b809-49c0f515b31b', '9f3d551a-0725-430e-897e-80ee9add3ae9' ,'HHG_INTO_NTS_DOMESTIC', 'i', true, now(), now(), 1), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The shipment type should be updated to HHG_INTO_NTS (remove DOMESTIC). I see we have B-21905 to update this so I think that BL should be an upstream to this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I saw that after I was already knee deep in this story so I figured since its just adding these records, it'd be okay to do the name change after. Tae's working the other story that's handling that name change and we had already talked about it. BUT I don't mind putting this on hold until his story gets in and then I can make the name change on this pr either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should be almost finished with name change story. Just need to test if anything is broken lol. I'd be okay with you holding this story until mine gets in. Then I don't have to do rename changes for your DB stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay sounds like a plan to me. I have to wait for a response from the gov anyway. So I'll hold this until yours gets in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes for renaming NTS is in IntegrationBranch now and you should be able to merge in MAIN-B-21905-rename-nts-shipment-type
to your Story Main branch and then make the name changes to your files -> then merge those changes here. This is the Main PR for ref.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added in the name change and the migration file from my main branch so this should be good to go for another review.
migrations/app/schema/20241208080706_add_internatinoal_nts_re_service_items.up.sql
Outdated
Show resolved
Hide resolved
I don't think so? or at least I thought the customer could add the storage address from their creation of the nts. |
Yeah we might have an upstream problem here because, in my head, if either the pickup/destination (in this case, pickup/storage) is OCONUS, the shipment needs to be international |
Yes, I would agree with that. |
Customer only provides the pickup address for NTS |
OOH okay. Well then yea in that case we were just talking about this earlier. Its a bug. And its a special case for ONLY this case on editing dNTS shipments for the first time the shipment market code doesn't flip to international when the addresses are changed to OCONUS. I was waiting on direction from our scrum master to see how to go about getting the process started on reporting the bug. |
Wouldn't that be a blocker for this work? |
I don't think so because the bug exists now in milmove. The code I'm adding works for this features AC. I think that bug has more to do with updating the shipment in general and that would effect more than the service items. But that's just my lowly dev thoughts lol I think this is a question for the government? |
A workaround - If you "edit shipment" for the 2nd time and then save with AK address - it switches to |
Is there an issue created for this bug? @KonstanceH @taeJungCaci |
Yea this^^ also they could create a new shipment for the marketCode change and delete the old one |
Yea @danieljordan-caci that was the part about waiting to hear back on how to report it lol |
Oh yeah I create issues all the time! Ideal process is to create the issue, provide analysis & fix, testers confirm, get PO to create a BL from the issue -> fix the issue |
oh nice! I'll get on it now and tag the issue in this pr |
Cool cool. For now if you can get a fix in for that nil check, rest looks good. |
Okay cool the issue is created adding it here for reference: |
if newShipment.MarketCode == models.MarketCodeInternational && | ||
(newShipment.PrimeEstimatedWeight != nil || | ||
if dbShipment.PickupAddress != nil && dbShipment.DestinationAddress != nil && | ||
newShipment.ShipmentType == models.MTOShipmentTypeHHGIntoNTS || newShipment.ShipmentType == models.MTOShipmentTypeHHGOutOfNTSDom { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This specific function is addressing updating estimated pricing for this shipment type. Has the upstream db functions/procs been updated to accommodate international NTS & NTSr shipments?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also are eliminating this check for iHHG moves, which is what it was originally created for.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay this should be good now. I'll see about these failing circleCI tests tomorrow @_@
B-21904
Summary
This PR adds in the pre approved service items for international NTS shipments.
Verification Steps for Reviewers
These are to be checked by a reviewer.
How to test
OCONUS -> OCONUS
OCONUS -> CONUS... etc
Approve and send
.International Shipping and Linehaul
andInternational Packing with NTS Pricing Factor
are preapproved service items.Fuel Surcharge - PODFSC
should only be pre approved if the shipment is OCONUS -> CONUSNote: OCONUS -> CONUS etc are determined by the shipments pickupaddress and storage facility address.
Example: NTS Shipment
Pickup Address -> Storage Facility Address == Ordering Type
Alaska -> Alaska == OCONUS -> OCONUS
Iowa -> Alaska == CONUS -> OCONUS
Backend
Database
Any new migrations/schema changes:
Screenshots
OCONUS -> CONUS
OCONUS -> OCONUS