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

Mark instance for deletion. 2nd iteration. Enable the user to mark an instance for deletion

    XMLWordPrintable

Details

    • Very Small (VS) < 1 day
    • 46
    • 88
    • R5
    • R4
    • R4
    • R1
    • R2
    • R1
    • R2
    • R4
    • R1
    • R4
    • R1
    • R2
    • R4

    Description

      The implementation of Mark for deletion work has been split into two iterations:

      1. UXPROD-3621
      2. UXPROD-3742

      Implementation: In Edit view implement a toggle which enable the user to mark an instance for deletion. Permissions are different than permissions for actual deletion.

      Slide deck: https://docs.google.com/presentation/d/1ePfp0_fK1xW4mfpS6NRIkFwDQEyAvqMPTAlXI8hbxCI/edit#slide=id.g1364ff8ecb1_0_14

      Technical backend note: The Inventory database has constraints defined on Instance, HoldingsRecord and Item to prevent deletion of entities with dependent records. The database will throw an exception if such a delete is attempted, as a last backstop - see:

      1. InstanceStorageAPI.java

      Out of scope: Prevent delete-all (wipe all data in Inventory). This functionality is used by SysOps doing migrations. The Core Platform is working on changing bulk deletion:

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                charlotte Charlotte Whitt
                charlotte Charlotte Whitt
                Charlotte Whitt Charlotte Whitt
                Michal Kuklis Michal Kuklis
                Votes:
                0 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases