Done
Details
Assignee
Viachaslau KhandramaiViachaslau Khandramai(Deactivated)Reporter
Viachaslau KhandramaiViachaslau Khandramai(Deactivated)Tester Assignee
Viachaslau KhandramaiViachaslau Khandramai(Deactivated)Priority
P2Story Points
2Sprint
NoneDevelopment Team
FirebirdFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Viachaslau Khandramai
Viachaslau Khandramai(Deactivated)Reporter
Viachaslau Khandramai
Viachaslau Khandramai(Deactivated)Tester Assignee
Viachaslau Khandramai
Viachaslau Khandramai(Deactivated)Priority
Story Points
2
Sprint
None
Development Team
Firebird
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 19, 2020 at 8:42 PM
Updated July 31, 2020 at 8:49 AM
Resolved May 25, 2020 at 11:45 AM
In order to fix bug from UIQM-14 with incorrect order of saved record fields one need to implement corresponding mechanism in scope of QuickMarcJson <-> ParsedRecordDto convertation.
Steps for reproducing:
1) Open record;
2) Edit record fields order and save record;
3) Open updated order.
Actual:
When fields are added in quickMARC, after saving the record and reopening the record in quickMARC or viewing the source record, the field appears at the top of the record, not where it was entered/added in quickMARC.
Related, I can move the field to the appropriate spot, save the record, and it will still appear at the top of the record. Fields that are added do not stay where they are place in quickMARC. They also move to the top of the record when viewing the source record or reopening quickMARC.
Expected:
Record should be reopened with saved fields order.
Acceptance criteria:
1) Record should be updated and reopened with saved fields order;
2) This case should be covered by unit tests.