-
We are looking into a similar feature. Just because we eventually have people (temporaritly) parting the company or don't want individuals to sign on again, but we don't want to loose context of the who the user was. side note: we are using an external auth provider (Entra ID).
-
-
We are looking into a similar feature. Just because we eventually have people (temporaritly) parting the company or don't want individuals to sign on again, but we don't want to loose context of the who the user was. side note: we are using an external auth provider (Entra ID).
Exactly the same use case for us. Would be great to have a full transparent history.
-
Name Previous Value Current Value Labels
empty Enterprise Edition
-
Previous Value Current Value Disable users or keep user name of deleted users
Able to disable users (instead of delete) to preserve activity history
-
OneDev
changed state to 'Closed' 9 months ago
Previous Value Current Value Open
Closed
-
State changed as build OD-6104 is successful
-
OneDev
changed state to 'Released' 9 months ago
Previous Value Current Value Closed
Released
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
Enterprise Edition
|
Issue Votes (1)
We are now in a situation that we have to disable access to OneDev for multiple users but there is no satisfying solution.
The requirements are:
Currently we can only delete a user but then loose context in issues etc or rename the user, e.g. "_disabled", and disable some notifications.