Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Firebird - Sprint 143, Firebird - Sprint 144
-
5
-
Firebird
-
Morning Glory (R2 2022)
-
Architecture issue
Description
Overview:
The issue was discovered on the Lotus bugfest but could not be recreated on the snapshot environment (Morning Glory version of the code).
Steps to Reproduce:
- Log into lotus-bugfest
- Go to Apps -> Settings -> Users
- Go to Fee/fine and check if there is an owner in Owners and if no - create it
- Go to Fee/fine and check if there is a transfer account and if no -create it
- Go to Transfer criteria -> Select Scheduled period (Days), select Schedule frequency (1), Schedule time (1 minute ahead from UTC), Fees/Fines older than (days) (1), Patron groups (Staff), Transfer owner, Transfer account, Fee/fine owner
- Click on Save
- Wait until 1 minute passed
- Go to Apps -> Export manager -> select Bursar as a Job type
Expected Results:
Successful status of export
Actual Results:
Nothing shown
Additional Information:
URL: https://bugfest-lotus.int.aws.folio.org
On Kiwi and Snapshots the issue is not reproduced.
Interested parties:
TestRail: Results
Attachments
Issue Links
- blocks
-
MODEXPS-129 MODEXPS (mod-data-export-spring) MG Bugfix release
-
- Closed
-
- clones
-
MODEXPW-172 Bursar scheduling does not work on Lotus bugfest
-
- Closed
-
- defines
-
FEXPCMN-10 Add tenant id to export config and job
-
- Closed
-
-
UXPROD-3497 Firebird - Morning Glory R2 2022 Enhancements/Bugfixes/Tech Debt
-
- Closed
-
- is blocked by
-
MODDICONV-252 Failure during enabling module for a new tenant
-
- Closed
-
-
MODEXPW-188 Remove asynchronous launching job for Bursar
-
- Closed
-
- relates to
-
MODEXPS-115 Bursar manually run works time to time on Lotus bugfest
-
- Closed
-