-
Notifications
You must be signed in to change notification settings - Fork 43
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
Settings of one facility persisting in another facility on changing the facility #500
Labels
Comments
R-Sourabh
added a commit
to R-Sourabh/bopis
that referenced
this issue
Jan 28, 2025
… are also being updated (hotwax#500)
1 task
R-Sourabh
added a commit
to R-Sourabh/bopis
that referenced
this issue
Jan 29, 2025
…Settings on Facility Update (hotwax#500)
R-Sourabh
added a commit
to R-Sourabh/bopis
that referenced
this issue
Jan 30, 2025
…hipment methods when the store does not change during a facility update(hotwax#500)
R-Sourabh
added a commit
to R-Sourabh/bopis
that referenced
this issue
Feb 3, 2025
R-Sourabh
added a commit
to R-Sourabh/bopis
that referenced
this issue
Feb 3, 2025
…tore changes upon changing the facility (hotwax#500)
ymaheshwari1
added a commit
that referenced
this issue
Feb 3, 2025
Fixed: On updating the facility, the settings related to the facility are also being updated (#500)
Issue verified and working fine in release v3.4.0 Hence, closing this ticket. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
Settings from Facility B are persisting and displayed in Facility A.
Expected behavior
Settings for Facility A should be displayed correctly and independent of Facility B.
Steps to reproduce the issue
Log in to the application.
Navigate to Facility A and modify or view its settings.
Change the facility to Facility B.
Open the orders tab and again navigate to settings tab.
Change the facility to A and check the settings for Facility A.
Environment details
App version : v3.3.0
App environment : UAT
Additional information
https://jam.dev/c/355371c4-74b4-46c9-b267-429d0979d33f
The text was updated successfully, but these errors were encountered: