Modify status of the completed export job
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
Attachments
3
has to be finished together with
relates to
Checklist
hideTestRail: Results
Activity
Show:
Kruthi VuppalaSeptember 5, 2020 at 11:35 PM
Also, the API tests are yet to be merged
Kruthi VuppalaSeptember 5, 2020 at 3:25 PM
verified on folio-testing using UI:
1. Run a job with valid UUIDs
2. Run a job with 2 valid UUIDs and 1 invalid
RESPONSE:
Igor GorchakovSeptember 5, 2020 at 1:15 PM
Verification details in https://folio-org.atlassian.net/browse/UIDEXP-145
Done
Details
Assignee
Igor GorchakovIgor GorchakovReporter
Magda ZacharskaMagda ZacharskaTester Assignee
Kruthi VuppalaKruthi VuppalaPriority
P3Story Points
3Sprint
NoneDevelopment Team
ConcordeFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Igor GorchakovReporter
Magda ZacharskaTester Assignee
Kruthi VuppalaPriority
P3Story Points
3
Sprint
None
Development Team
Concorde
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created August 3, 2020 at 6:35 PM
Updated September 6, 2020 at 12:02 AM
Resolved September 5, 2020 at 3:25 PM
Purpose/Overview:
Currently when the job completes and the export file is generated the job status is set to Success. However, sometimes the file is created but only a part of the export succeeds due to some records erroring out.
Requirements/Scope:
For the jobs that exported successfully are the records set the status to: Completed
For the jobs that exported with some errors to: Completed with errors
Corresponding UI story is https://folio-org.atlassian.net/browse/UIDEXP-145
Acceptance criteria:
The appropriate status is displayed for jobs with and without errors
Migration scripts are created and tested
Unit tests are written
API tests are updated/written