-
Notifications
You must be signed in to change notification settings - Fork 37
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
No Shipping Method Setup Leads to Blank Option in Dropdown on Order Detail Page #649
Comments
Will add UI here |
@Adameddy26 please review jam video since it doesn't seem to be connected to the issue you mentioned. Need more details |
Clicking on the information button will link to this doc: |
Corrected the same. |
Improved: Displayed message string when no shipment method is linked to the selected carrier (#649).
Issue verified in release v2.8.0 and found that message 'No shipment methods linked to ' is not visible when user navigate back to same page after switching the tab/section. Hence, reopening this issue. |
Fixed: Displayed message correctly when there is no method associated with carrier (#649).
Issue verified and working fine in release v2.8.1. Hence, closing this ticket. |
…ted with carrier on the generate tracking code modal (#649).
Improved: Displayed message if there are not shipping methods associated with carrier on the generate tracking code modal (#649).
Current behavior
A blank option appears in the dropdown, causing confusion and potential errors in order processing.
Expected behavior
If no shipping method is set up, the dropdown should either display a message such as "No shipping method available" or be disabled to prevent user interaction.
Steps to reproduce the issue
Navigate to the order detail page of In Progress page.
Select the carrier and then open the shipping method dropdown.
Observe that a blank option is displayed if no shipping method is set up for the selected carrier.
Environment details
App version : V2.7.0
App environment : UAT
Additional information
https://jam.dev/c/9077cf41-9619-4ab5-b119-ffef0281f039
The text was updated successfully, but these errors were encountered: