Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Export time is set as when configuration is saved rather than the time chosen in the UI

Description

Overview: When creating a new Organizations export configuration. The export time is set as when configuration is saved rather than the time chosen in the UI

Steps to Reproduce:

Case 1

  1. Log into some FOLIO environment as User X

  2. Click on an Organization

  3. Add a new integration

  4. be sure to include FTP details

  5. Schedule export for hourly and select a time that is 10 minute from the current time.

  6. Note the current time when saving the export

Expected Results: Configuration is saved and export job is run 10 minutes later at the specified start time. New export job is run every hour from that time

Actual Results: Export job is created immediately (Current time). every hour from that time a new export job is created.

Case 2

  1. Log into some FOLIO environment as User X

  2. Click on an Organization

  3. Add a new integration

  4. be sure to include FTP details

  5. Schedule export for hourly and select a time that is 10 minutes earlier than the current time.

  6. Note the current time when saving the export

Expected Results: Configuration is saved and export job is run 50 minutes later at the specified start time. New export job is run every hour from that time

Actual Results: Export job is created immediately (Current time). every hour from that time a new export job is created.

 

Additional Information: This behavior makes the time input necessary. It also makes it impossible for the user to schedule an export to run in the future.

URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Note that the start time used will actually the time you save the configuration rather than the time you have indication under scheduling details.

Attachments

4
  • 23 Aug 2022, 11:02 PM
  • 23 Aug 2022, 09:48 AM
  • 16 Aug 2022, 10:33 AM
  • 16 Aug 2022, 09:35 AM

Checklist

hide

TestRail: Results

Activity

Show:

Dennis Bridges August 24, 2022 at 4:07 PM

Core of this issue has been resolved. Remaining issue is lower priority so https://folio-org.atlassian.net/browse/MODEXPS-145#icft=MODEXPS-145 was created to track it and it has been assigned to the next release.

NinaChistova August 24, 2022 at 7:31 AM
Edited

Hello ! An issue only with "Daily" frequency reproduces for all organizations, separate issue https://folio-org.atlassian.net/browse/MODEXPS-146#icft=MODEXPS-146 was created. Issue does not reproduce with Hourly, Weekly and Monthly frequency.

Dennis Bridges August 23, 2022 at 11:02 PM
Edited

In my testing the export is still running automatically. Can you try this test with the same organization. Perhaps this is because I've changed the Frequency to Daily?

It seems like it may be an issue with just this one organization...Hoping someone else might be able to determine the cause so we can be confident that this issue has been resolved.

NinaChistova August 23, 2022 at 9:48 AM

Tested on https://bugfest-mg.int.aws.folio.org/

Works as expected

please review

Oleksii Petrenko August 22, 2022 at 5:19 PM

Deployed to MG bf. Please proceed with verification.

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Thunderjet

Parent

Fix versions

Release

Morning Glory (R2 2022) Bug Fix

RCA Group

Implementation coding issue

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created April 18, 2022 at 5:06 PM
Updated August 24, 2022 at 4:07 PM
Resolved August 17, 2022 at 3:09 PM
Configure
TestRail: Cases
TestRail: Runs

Flag notifications