Idea ID: 1686875

RecycleBin for ALM Octane

Status : Accepted
over 2 years ago

If a user deletes an entity (e.g. Requirement, TestCase, Epic, User Story, ...) then the entity is immediatelly deleted in the ALM database.

If then the user raise a ticket with internal ALM support that entities were deleted by mistake the support has not really a chance to restore the whole database.

For ALM/QC .NET we have already introduced special admin-roles which are only allowed to delete, but even then it happens that entities are deleted by mistake. Therefore we have implemented further in ALM/QC .NET workflow code which introduce a recycle bin and a 4-eyes deletion feature.

In ALM Octane the implementation of such new own feature is not possible so far.

Therefore the question is whether ALM Octane will introduce an own 'RecycleBin' function, that a user first has to move entities to a RecycleBin before it can be physically deleted by e.g. the local workspace admins. Or maybe the enties are deleted in the GUI, but still remain in the database for some time, before they are physically deleted (and e.g. the local workspace admin has the possibility to bring the entities back into the GUI if needed).



  • Recycle Bin for defects is now available on Octane release 15.1.90, more entities (manual tests, work items, requirements etc) will be supported in future releases.



  •  when can we expect this?

  • thanks for that  

    Can you please advise if this has been implemented in either 15.1.20 or 15.1.40 releases of Octane?

  • Hi  

    thank you for this feedback, we are now designing the solution for Recycle Bin implementation in Octane and I can confirm that every action will be audited (moving entity to recycle bin, restore from recycle bin, permanent deletion from recycle bin) and that in addition we will provide a way for the admin to permanently delete recycled entities but that would be a manual action upon permissions so that each organization can comply with their retention policy




  • We also require this functionality but for two reasons:

    1. We work with a 7 year retention policy which means that all records need to be maintain until our Information management group approves the destruction of any production information.
    2. Restoration of accidental delete as discussed above.

    I have not had the time to look yet but we also need Audit logging to ensure that the delete process recorded.