Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Automatically Reassign Objects When Deactivating a User

Avatar

Level 5

05-01-2018

When a user is deactivated, their open issues, tasks, and projects often need to be transferred to their replacement. A way to automatically do this from the deactivation window would save admins from finding objects and reassigning them manually.

8 Comments

Avatar

Level 10

05-01-2018

Love this idea!

However we have an integration with our HR system to auto deactivate users. BUT.... wondering if there could be something in the Setup area (like Recently Deleted items in the recycle bin) that System Admins and the new Group Admins could go in to see who was recently deactivated and then have an option to reassign everything that is still open/active to someone.

Avatar

Level 1

05-01-2018

This is a fantastic idea and especially relevant with enterprise-level clients, where users are constantly moving around the enterprise or as part of role turnover.

Avatar

Level 2

28-09-2018

Agreed! This should also prevent unintended assignment when importing MS Project plans which we've experienced recently.

Avatar

Level 1

29-03-2019

the reassignment of tasks (project ownership as well) would also be considerable benefit for prolonged absences due to medical leave, sabbaticals, and the like

Avatar

Level 10

11-12-2019

Open issues, tasks and projects are the least of our worries. The footprint of a user can expand to objects they own and share with other users whose access can be impacted by deactivation. For example, deactivating a user will render their shared calendars unusable. In addition, the meaning of "automatically transferring" can be complicated, for example if an entire team decides to evenly share the work of the deactivated user, we would want to be able to indicate that project ownership (for example) is left out so we can do this manually. What I would prefer to see is a clear way to indicate the user's footprint in an efficient way (we currently do this through a dashboard with prompts and the same user ID is filled in about 10 or 15 times, and there are still items that we cannot report on, so better reporting functionality is also desirable)