-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update UI for the route page #181
Comments
Added support to save the status for group on change instead of button click Changing the schedule will display an alert to save changes Moved the batches section to right Added button block to the description card when no description is present Updated the fab button for saving unchanges to ion-button at the bottom of batches list
…the save button, if clicking cancel reverting the value for schedule to previous value(hotwax#181)
Improved: UI for the route page as per the figma(#181)
Implemented: support to edit groupName(#181)
As we need to save the unarchived routings on clicking backdrop, thus added support to directly update the routing status state on clicking unarchive button instead of waiting for the user to close the modal, becuase after unarchiving multiple routings if user clicks backdrop the data is not passed to parent component and the routings are not updated. Improved the case to display archived routing card when we have all the routings as archived
Fixed: case related to updating archived routing and its UI(#181)
#182 - https://jam.dev/c/93361b3f-191c-4c8c-a449-67a5ab756375 All changes of related to updated UI are verified and working fine in release v1.2.0. https://jam.dev/c/a71dd76d-c593-4c85-80de-27b8fde78a9a |
Fixed: archived routing cards to be dispalyed correctly after unarchiving a rule(#181)
Issue verified and working fine in release v1.2.1. Hence, closing this ticket. |
What is the motivation for adding/enhancing this feature?
What are the acceptance criteria?
Can you complete this feature request by yourself?
Additional information
The text was updated successfully, but these errors were encountered: