Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.1.0
-
Labels:
-
Template:customfield_11100 23867
-
Sprint:EPAM BatchLoader Sprint 11
-
Story Points:1
-
Development Team:Folijet
-
Epic Link:
Description
Overview: Bug from UIDATIMP-79. When saving a valid file extension setting (either to allow or block import), the unsaved changes modal appears, but it shouldn't.
Steps to Reproduce:
- Log into FOLIO-testing or FOLIO-snapshot as diku_admin
- Go to settings/data import/file extensions
- Create a new file extension, either to block import or allow import
- Press Create button
Expected Results: New file extension setting is saved, and user is returned to the list of file extension settings
Actual Results: Unsaved changes modal appears. If you click "Keep editing" and then close the create window, you'll see the file extension setting has actually been created
Additional Information: See attached video
TestRail: Results
Attachments
Issue Links
- relates to
-
UIDATIMP-79 Data import settings page's 3rd pane for File Extensions: Save the new file extension
-
- Closed
-
-
UXPROD-1376 CRUD for File Extensions
-
- Closed
-