Recycle Bin/ Archive feature in ALM Octane

Recycle Bin/ Archive feature in ALM Octane

Hi,

Present Situation:

Scenario: 1st

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

It's and not a good idea to restore the whole database because we can lose data.

Scenario: 2nd 

Admin wants to archive and hide old entity (e.g old Test cases, Epic, etc.), it's not possible.

Idea: 

It's good to have a Recycle bin  feature before to  final delete

It's good to have entity Archive feature.

 

Thanks

8 Comments
Jesper Honored Contributor.
Honored Contributor.

You can just implement rules which prevent deletion of certain entities....

Then users can just rename and reuse instead of deleting and creating

Also creating an area under application module/backlog called "To be deleted" and then users can move stuff here instead.

But would be nice with a Recycling bin in the Backlog/App module and Requirement where deleted entities would stay for a predefined period of time. Once moved to the Recycling bin in one of the 3 locations it would also be moved in the others

Knowledge Partner
Knowledge Partner

Yes this would be nice feature. 
actually we have it also in old ALM and this is missing here.

Sauer
Member.

One nice change could since a test can be set to obsolete, default all searches to hide obsolete tests/tasks so there is less to search through. Would just change the process for tests, but that's one way we currently help search through our tests.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted
 
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Accepted

Indeed a valid request.
We have the Recycle bin functionality on our backlog, though no planned delivery yet.

testservicecent Respected Contributor.
Respected Contributor.

Makes definitely sense to implement this for normal entities like epic, story, feature, defect, ....

Within the customization area it is already implemented in a way that e.g. Users, Phases, Fields, Listboxes are not physically deleted. They just change the internal ACTIVITY_LEVEL to 2 (which means deleted from a GUI perspective). But I have not found a way yet how to 'reactivate' a user after he was deleted. The system will create a new user with new ID

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

If you choose to delete an item, it cannot be reactivated after.

for the option to reactivate you should select the Deactivate functionality (for users, list items, releases etc) and not the delete option.

in GDPR mode for example, as part of the right to be forgotten, if you delete a user, all the user data is completely deleted from the system. 

therefore - the recommended flow is first to deactivate an item, and only after you make sure it will no longer be needed, use the delete option.

hope that clarifies,

regards,

Sigal

 

 

testservicecent Respected Contributor.
Respected Contributor.

So far we are not using that heavily Octane, but we plan to replace ALM.net with Octane, and in ALM.net we have around 20.000 active users in SiteAdmin, whereas over the last 8 years we deleted additional 63.000 users (because we don't want to have > 80.000 users where 75% of them is deactivated). In ALM.net it is not an issue to recreate an user, because in all entities (like Defects, TestCases, Requirements) the user-id is stored as text, therefore the user can still filter/group/search for the old entities.

Whereas in Octane it is stored as numeric ID. But in the moment we recreate the user again it is creating a new user ID. As a result you will see in e.g. Defect module entities e.g. created by same name, but internaly stored for two different user ID. Therefore filter/group/search will find only for new user ID.

And unfortunatelly it happens in such a big organization that especially external colleagues leave the company, and 6 month later they are back.

As mentioned, so far this is not an issue for us, but maybe it will become an issue, just wanted to bring this up here as a discussion point

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.