Bulk edit: jobs start_time and end_time in the database and the Export manager can be irrelevant for jobs IN_PROGRESS

Description

Bulk edit: jobs start_time and end_time in the database and the Export manager can be irrelevant for jobs IN_PROGRESS.

Steps to Reproduce:

  1. Log into some FOLIO environment as a User

  2. Run bulk edit job ( example: 1000 item barcode records)

  3. Go to the Export manager or database to observe the job status. The status should be IN_PROGRESS

Expected Results:

We can observe the actual start_time displayed and null or empty field for end_time
Actual Results:

In the database, the start_time of the job is equal to the SQL query start time. On the Export manager page, start_time is equal to the last page refresh.

end_time is equal to the start_time.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

8
  • 05 May 2023, 01:33 PM
  • 05 May 2023, 01:33 PM
  • 05 May 2023, 01:33 PM
  • 05 May 2023, 01:33 PM
  • 05 Apr 2023, 12:09 PM
  • 05 Apr 2023, 12:08 PM
  • 05 Apr 2023, 12:00 PM
  • 19 Sep 2022, 12:42 PM

Confluence content

mentioned on

Checklist

hide

TestRail: Results

Activity

Show:

Yauheniya Kryshtafovich May 5, 2023 at 1:34 PM

Hi, and verified on Snapshot env, works as expected:
1. User is on the "Bulk edit" landing page
2. Upload a .csv file with big number of users' UUIDs by dragging it on the "Drag & drop" area. And till Bulk edit job is In progress, go to the "Export manager" and pay attention to the "Start time" and "End time":

  • "Start time" is equal to the time job starts running

  • "End time" is empty till job in progress


    3. Check "Started" and "Ended" columns on the "Logs":

  • "Started" is equal to the time job starts running

  • "Ended" is empty till job in progress


    4. The "Preview of record matched" accordion shows a table populated with the records that related to the uploaded identifiers:
    From "Export manager" and "Logs" the "Start time" and "End time" are equal to the time job starts and ends running
    5. Complete Bulk edit =>
    From "Export manager":

  • "Start time" is equal to the time job starts running uploading identifiers

  • "End time" is equal to the time job ends running uploading identifiers


    From "Logs":

  • "Started" and "Ended" are equal to the time Bulk edit starts and Bulk edit ends

Mikita Siadykh April 28, 2023 at 7:31 AM
Edited

   I believe what provided above is incorrect: end time in bulk operation shouldn't be equal with end time in Export manager as it is used only to generate file with records and not for whole bulk edit flow as it was before

 

  please verify that Export manager job (not whole bulk operation) has right start-end values

 

cc  

Olga Kondratenko April 5, 2023 at 12:09 PM

If you will run the query
select * from [tenant]_mod_bulk_operations.bulk_operation order by start_time desc limit 100

 

You will see time for all bulk edit operations to find records and update them.

In UI Export Manager we can observe only the time of the first part of the job(finding matched records).

Job type - "Bulk edit identifiers" for all of the bulk edit jobs.

Viachaslau Khandramai April 5, 2023 at 11:34 AM

, is it still reproduced? I asked because we completely refactored bulk edit and move it to bulk operations.

Magda Zacharska February 25, 2023 at 2:34 PM

and - is this still applicable after refactoring?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Firebird

Fix versions

Release

Poppy (R2 2023)

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 19, 2022 at 12:41 PM
Updated May 5, 2023 at 7:05 PM
Resolved May 5, 2023 at 7:05 PM
TestRail: Cases
TestRail: Runs

Flag notifications