Uploaded image for project: 'WORKTERRA'
  1. WORKTERRA
  2. WT-10897

Import Record summary should have unique identification

    Details

    • Type: Bug
    • Status: In LB Testing
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: BenAdmin
    • Labels:
    • Environment:
      Production
    • Bug Type:
      Functional
    • Bug Severity:
      Medium
    • Module:
      BenAdmin - Import
    • Reported by:
      Harbinger
    • Item State:
      LB QA - On Hold
    • Sprint:
      WT Sprint 37 - Bugs

      Description

      To show number of records imported, sent to bad, a third table is used.
      The table do not identify the record uniquely and only returns the top record. So if there's a parallel import, scenario may occur that statistics of two imports are swapped depending on which completes first.

      ImportExportBadFileID can be used as unique key for import to solve the issue.

        Attachments

          Issue Links

            Activity

            Transition Time In Source Status Execution Times
            Snehal Katkar (Inactive) made transition -
            Open In Development
            20d 2h 5m 1
            Jayshree Nagpure (Inactive) made transition -
            In LB Testing Stage Testing
            25d 18h 21m 1
            Jayshree Nagpure (Inactive) made transition -
            Stage Testing Reopened in Stage
            2d 19h 44m 1
            Jayshree Nagpure (Inactive) made transition -
            Reopened in Stage In Development
            3s 1
            Jayshree Nagpure (Inactive) made transition -
            In Development In LB Testing
            7d 7h 18m 2

              People

              Assignee:
              jayshree.nagpure Jayshree Nagpure (Inactive)
              Reporter:
              suraj.sokasane Suraj Sokasane (Inactive)
              Developer:
              Snehal Katkar (Inactive)
              QA:
              Jayshree Nagpure (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:
                Production Due Date:
                Code Review Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 12h Original Estimate - 12h
                  12h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 36.5h
                  36.5h