Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2615

Ability to kill a long-running or errored data import

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Development Team:
      Folijet
    • Calculated Total Rank:
      83
    • PO Rank:
      101
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R3
    • Rank: Grand Valley (Full Sum 2021):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      When a data import is taking too long (and may have died without an indication), user should have the ability to manually stop that data import job.

      TBD: when a job is stopped, what should happen?

      • Retain as much as had created/updated properly, and add to log as Completed with errors?
      • Roll back everything that may have created/updated, and add to log as Failed?
      • Any indication needed that a user stopped the job (and if so, who)?
      • What else?

      Question - what about existing jobs that are stuck (see EBSCO demo account for examples). Can they be retroactively updated so that they can be stopped?

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases