Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-651

Add capability to remove jobs that are stuck in "Running" area of Data Import landing page first pane



    • Folijet Sprint 98
    • 3
    • Folijet
    • Simmons


      Purpose: Sometimes jobs get stuck in the Running area of the Data Import landing page, when modules crash. They never finish, and they never disappear. We need a way to remove them from that area of the landing page. This story reuses most of the functionality we use when deleting a file that was not supposed to be uploaded. See scenario 2 of UIDATIMP-38

      As a staff member using data import
      I want to clear out the stuck jobs in the Running area of the landing page
      So that I only see jobs that are actually running, and there is no clutter of long-dead/long-stuck jobs


      1. Scenario 1:
        • Given the Data Import landing page
        • When viewing each card for a "Running" job in the first pane
        • Then add a trash can icon to the top right of each card
      2. Scenario 2
        • Given the trash can icon on a Running job card
        • When a user clicks it
        • Then change the card to red
        • And replace the trashcan icon with an Undo button
        • And change the card text to [Job name] [dot] [file name] has been stopped
      3. Scenario 3
        • Given the Undo button on a Running job card that the user has clicked to delete
        • If a user clicks Undo within 10 seconds
        • Then restore the card to its normal appearance in the Running area
        • And do not stop or fail the job
      4. Scenario 4
        • Give the Undo button on a Running job card that the user has clicked to delete
        • If a user does not click Undo within 10 seconds
        • Then send a stop/fail message to the backend
        • And remove the card from the running area
        • And add the job to the top of the job log with a status of Completed with errors or Failed, whichever is appropriate
      5. Scenario 5
        • Ensure this story passes Accessibility testing
      6. Scenario 6
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See video and mockups below.

      Per OleksiiKuzminov we can do 1 and 2 below in the scope of this story. Step 3 will need to wait until the Rollback feature (UXPROD-1383)

      • Step 1: Stop and mark as error (secret button and PubSub profiles)
      • Step 2; Stop and delete/rollback all related records - MARC, Instances, Holdings, Items) (secret button only, since it only creates SRS MARC and Instances)
      • Step 3: Stop and delete/rollback all related records (for PubSub profiles, across all apps, create/modify/update) Note that Creates will be easier than Modifies or Updates

      NOTE: This should have a separate permission from regular Data Import permissions. See UXPROD-1384 for Data Import permissions

      TestRail: Results


          Issue Links



                Ihor_koba Ihor Koba
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                3 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases